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.
That's called sharding and is pretty widely used nowadays. There is even readily available middleware that handles this for you, so no need to put it into the backend.
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.
Pretty certain we were at the same conference. There development practices horrified the group I was with in the audience. At a time that a new competitor appeared (Facebook) they made the fatal mistake of rewriting their software in dot Net. No new features for a year or more. Joel Spolsky wrote a pretty famous essay about the wisdom of doing that.
I had an older friend that worked at CF when I was a teenager. He taught me a bit about relational databases and some other important stuff as he was one of the only developers I knew growing up.
I remember him telling me how I was wasting my time building in php/MySQL since CF was the future and serious companies wouldn't be looking for php developers. Glad I never pulled the trigger and bought their expensive IDE.
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!"...
Hilariously, ColdFusion strikes again. I should have used pound signs around the bad_memories variable. The above code would dump the string "bad_memories".
dhosek|5 years ago
411111111111111|5 years ago
That's called sharding and is pretty widely used nowadays. There is even readily available middleware that handles this for you, so no need to put it into the backend.
DaiPlusPlus|5 years ago
Break middle-school students' copypasta CSS rules for animated GIF backgrounds at your peril.
83457|5 years ago
rmason|5 years ago
https://www.joelonsoftware.com/2000/04/06/things-you-should-...
jjeaff|5 years ago
I remember him telling me how I was wasting my time building in php/MySQL since CF was the future and serious companies wouldn't be looking for php developers. Glad I never pulled the trigger and bought their expensive IDE.
bigiain|5 years ago
hestefisk|5 years ago
zingermc|5 years ago
zingermc|5 years ago
Corrected:
<cfdump var="#bad_memories#"/>