My wife worked there for the transition. Her very first .net page was the MySpace homepage (which was demoed by Steve Ballmer at CES, iirc). Microsoft was very unhappy with the decision to retain the .cf extension on web pages even after the transition to .net. There were some crazy levels of scaling happening behind the scenes—they had database requirements beyond the capabilities of sql server and there was code on the server side to route to different sql clusters based on the user's numeric id. They also had more page views than they could sell ads for. There was actually a pretty crazed level of new feature development happening at the same time—any time that friendster or some other site would release a new feature, Tom would insist that it be implemented on MySpace right away. At the same time, he was also requiring things like pixel-for-pixel identical output for existing pages/features through all of this.

I was at a CF conference with MySpace as a speaker and they talked about how often they went down but that they were switching to another CF engine with .net capabilities (BlueDragon). Their discussions and jokes about instability and going down due to bad code updates were really cringy and gave the impression that their platform was a mess.

For proper early 2000s nostalgia, I reckon the backend should actually be Apache mod_perl, with the ".cfm" extension script aliased to Perl CGI scripts because management tell everybody "it's running on Adobe!"...

<cfdump var="bad_memories"/>