Windows 8 will (probably) not deprecate C++ and .NET in favor of HTML5
New APIsThere will be two new core APIs in Windows 8 that both C++ and .NET can use:
- WinRT: a modernized version of the Win32 API.
- DirectUI: a new UI API that brings some of the comfort of the .NET-only WPF to all of Windows (XAML etc.).
The point of all this? It gives parity to native C++ and managed .NET code. Instead of being separate, each with its own different capabilities and strengths, they will be peers. If Microsoft adds new APIs to core Windows, the WinRT system will ensure that they're seamlessly available to managed code, meaning that .NET developers will no longer be at a disadvantage relative to native ones. Conversely, existing native applications can be updated to use the new UI without having to be substantially rewritten to use .NET. This same flexibility applies to Microsoft: putting native and .NET code on an equal footing opens the door to actually seeing .NET applications shipping with the operating system.
C++ and .NET versus HTML5 on Windows 8Quote:
Microsofts silence. Quote:
It's understandable that Microsoft doesn't want to spill everything right now. Windows 8 is still a long way from completion, and plenty could change between now and BUILD. But developers aren't asking to hear everything now; they want to know a few salient details. Answering two questions would probably do the trick.The answer to both questions is likely yes. Additionally, one will be able to write first-class applications with many native features in HTML5. It is strange that Microsoft will wait until the BUILD conference in September 2011 to spread the good news.
- Will it be possible to write immersive applications using C++ or .NET?
- Will it be possible to write immersive applications using XAML?
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)