@felix9: "the only exception may be the phone. but Apollo is the son of Jupiter IIRC. "
Loading user information from Channel 9
Something went wrong getting user information from Channel 9
Loading user information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
I guess I wasn't a developer at the time so I'm not sure what all the differences between Win3.1 and Win95 were from that perspective. From an end-user POV the main difference was the new shell. "The biggest change since ..." isn't exactly something objective that can be rigorously defined, so there will always be different ideas of what does or doesn't justify it, but it's at least a plausible claim based only on what we know.
The name change is because they want to attract a wider audience, and the secrecy again is because they're trying to figure out how to woo a new audience that is very suspicious of them, and they're trying to be very careful about how they do it.
"They are also touting this as the biggest thing since Windows 95. That's a hard sell. Therehas to be a reason, and it's not HTML5/JS."
er, new touch shell, new touch UI, new app distribution/deployment and sandboxing model, new cloud integration stuff, support for a new processor architecture, new C++ APIs, new COM replacement/revamp? And new HTML/JS integration as well. Seems to already meet that standard, just from what we already know.
Yeah, I really doubt there will be any magical IL to JS compiler. The problem with that is it's hard to make it efficient because it's an abstraction inversion, i.e. translating from something lower-level to something higher-level, and that just doesn't work very well. The native, managed and platform integration story will be "call DLLs through the Windows Runtime", where WinRT is basically a new version of COM/ActiveX designed to allow more idiomatic JS APIs, more secure sandboxing, etc. The reason they're being so secretive about it is they're trying to work out how to explain/spin this to the non-Microsoft-oriented web developers they're trying to court without them hearing "ActiveX" (which is what it basically is), and running for the hills
""Legacy" means they won't develop it further. WPF and Silverlight both need more work. That really speaks of a premature taking out to pasture. You could also say that Microsoft doesn't see them worth fixing. Kinda like linq to sql getting an early culling by the premature birth of EF. Yeah they really went to town on Linq's designer after EF was in incubation."
Weirdly the new embedded database API in Windows Phone Mango is a version of LINQ to SQL, not EF or straight SQL/ADO.NET or something new. It even adds a few new features not in the desktop version. So I guess not everyone at Microsoft thinks L2S is dead ...