2 ms·
Yeah, I don't think there was any "golden age" for MS coders. Each individual tier gets to a point of "okay, now we've got this figured out" and then they depr
by Pxtl 13y ago
Yeah, I don't think there was any "golden age" for MS coders. Each individual tier gets to a point of "okay, now we've got this figured out" and then they deprecate it and give you a new mess from scratch.
The biggest disappointment is how many times they've started from scratch within the .NET framework. The constant churn of database APIs mentioned in the article is a great example. Finally now MS has followed a more open-source-ish development process with EF.Net and MVC - ironically by switching to faster iterations I feel more confident using it because I know it's being well cared-for and won't get abandoned and deprecated.
The big disappointment is how .NET has failed to be "write once run anywhere" even within Microsoft's universe. Every platform except the server gets a restricted subset of it, and you often don't find out that your subset is unavailable until run-time.