MySpace wasn't always .NET. It was ColdFusion before .NET v2 came out. Not that ColdFusion would have made any difference. That said, I'd argue that no, Micr

MySpace wasn't always .NET. It was ColdFusion before .NET v2 came out. Not that ColdFusion would have made any difference. That said, I'd argue that no, Microsoft did not kill MySpace. Generalizations like this are wrong. There are many more .NET enterprise developers out there then there are Ruby or Node or Python. With quantity comes a varying degree of ability. MySpace killed themselves by lowering their standards to the easy-to-find .NET developer instead of setting the bar higher. Once you lower the standard by which you hire developers, it's a cycle. The new guys will lower the standard a little more to hire the next set, etc. The lesson to be learned here is if you can't find a good developer, don't blame the technology stack you've selected, blame your recruiter. Find the person you want, they are out there.