For some unknown reason, MySpace decided that instead of using the standardized monolithic file for OpenSocial (that developers host on their own servers) they would host the code themselves on their servers. This type of caching is great since it puts the burden on MySpace to keep applications available to their users, but it has an unintended consequence. One accidental database and your entire code base goes away. As a developer it’s frustrating enough to have to cut and paste code into their web pages or even just edit directly in their UI. This type of backup free zone and lack of revision control is very dangerous and challenging for developers. Today is a perfect example of why this was a REALLY bad idea.

Tags: myspace, opensocial

This entry was posted on Tuesday, March 4th, 2008 at 12:49 pm and is filed under code, technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.