Re: whoopee, ".Not" got something that C++ already had for, like, EVAR
Trying new things is called "innovation". Sometimes it works, a lot of the time it doesn't (Microsoft seems especially good at this side of the equation), but without it, we wither and die.
True ... but probably unimportant.
.Net was conceived as Java with a Redmondian accent, back when Sun Micrososytems were getting shirty with Microsoft for putting non-portable things in to Java. If there was innovation then it was Sun's not Microsoft's.
Actually, though, I'm not sure there was innovation, as the only "new" thing in Java was that it used an interpreted intermediate code that could be run on any platform -- and, in particular, in a browser ... and the only part of that that was new was targeting the browser, because UCSD did the intermediate code for portability thing with their Pascal P-System 20 years earlier.
Just think what good tooling for C++ we might have today if Microsoft had taken all the resources they threw at .Net and used them to improve the C++ development environment instead! Just think of the fancy debuggers, profilers, refactoring editors, and all the other stuff they might have been able to develop if they hadn't wasted their effort on an unnecessary runtime environment that nobody needed.
Microsoft ended up buying a slice of Sun, anyway, so the spat over Java went away. They didn't need to invent C-Hash and port all their huge codebase of Java to it ... they could have got on with something that produces material benefits for their users, instead!