Linked by Thom Holwerda on Fri 22nd Mar 2013 16:31 UTC
Windows Paul Thurrot: "Tipped off by a reader, I checked my System log in Event Viewer today and what did I find but a stack of pending updates for all of the core apps in Windows 8. I'm not 100 percent sure this is what I think it is. But if we're right, it looks like 18 of the core apps in Windows 8 are about to get updated. Or, almost all of them." Foley confirms it. By far Windows 8's weakest link, so I'm hoping this is true. Especially the Mail application is dreadful.
Permalink for comment 556528
To read all comments associated with this story, please click here.
RE[5]: Comment
by moondevil on Mon 25th Mar 2013 07:30 UTC in reply to "RE[4]: Comment"
Member since:

I think .NET vs WinRT is a bit a consequence of Vista's failure.

When .NET came out, the idea was to migrate everything to .NET, and C++ got a second class status.

There were two attempts to bring C++ developers to .NET world, first with Managed C++ and with .NET 2.0 C++/CLI.

Additionally, not all wannabe .NET developers, even today, are aware that you can compile to native code on installation time via NGEN.

Vista suffered a bit from the typical over engineering that is part of so many enterprise projects, which lead partly to its failure.

This allowed the Windows division, which isn't a big .NET fan, to make the Tools division go full circle back to native code.

This is why we have the C++ Renaissance, most of the new Windows APIs since Vista are COM based and not Win32, and finally WinRT offers a .NET like experience for native languages.

Even C++/CX is a set of C++ extensions, which although similar to C++/CLI, are used in native code.

While I don't like them, they are no different than C++ Builder's language extensions, or the ones almost every C or C++ compiler offers.

For those that are not aware, .NET applications are actually compiled to native code in Windows Phone 8, and according to some job offers on Microsoft, they might eventually integrate Visual C++ backend with native code backend for .NET.

Personally, I think the best way would be just to have a direct to native code compiler for .NET, or improve NGEN optimizations. But the political wars between Microsoft divisions have most likely lead to WinRT, which was in part the initial design for .NET, before they adopted the bytecode model.

This is nothing new, I have a few scars from political wars between software teams in Fortune 500 companies.

Reply Parent Score: 2