The most likely model I see coming out of Build is one where a lot of the functionality of WPF/SL, in the form of XAML, is moved directly into the OS and build on top of a new version of whatever they're calling DirectX these days. That way native code in the form of WinC++ would be able to use it, managed code in the form of C# and VB.NET would be able to use it and be faster, and the HTML/JS stuff they're trying to cram down our throats would either compile/interpret down either to it or, more likely, to exposed APIs from IE that would be built on top of the same thing as the now native XAML. I think they are basically going to give us three new app paths: native (C++), managed (.NET), and web-like (HTML/JS) plus legacy native and .NET support for Intel based systems.
I find it extremely unlikely that any fairly full featured app built for Windows 8 using HTML/JS is going to run very well in a browser on another OS however. It is most likely going to be taking advantage of Windows native libraries that just aren't available elsewhere.
Discussion on:
Message 12 of 1
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
