
To view parent comment, click here.
To read all comments associated with this story, please click here.
How would WinRT be able to replace Win32 when WinRT itself uses Win32? See e.g. http://arstechnica.com/features/2012/10/windows-8-and-winrt-everyth... for an in-depth explanation on this.
beat me to it, WinRT is built on Win32.
I agree that in one sense i would prefer more compeition as even apple has been a little lax with their design because they think they own the market.
I also agree with Google, why spend resources on a platform that may not fully play out, when they get a bigger share Google will develop for them, Google gets its revenue from access their web services, they don't really care how you do it, laptop, windows, mac, android as long as you connect.
How would WinRT be able to replace Win32 when WinRT itself uses Win32? See e.g. http://arstechnica.com/features/2012/10/windows-8-and-winrt-everyth... for an in-depth explanation on this. "
It makes use of Win32 today, no one can say how it will look like in Windows 9, or whatever it is going to be called.
would ==> indicating a possible (but not definite) future action or state
Gee, why do people have to try to explain this every time, without imagination how it might look some releases ahead.
Because WinRT is an abstraction ontop of Win32, it can just as easily have Win32 removed in the future with consumers of the WinRT being none the wiser.
People always point this out "WinRT is built on Win32" as if it matters. .NET is built on Win32, but you don't really say you as a developer are consuming Win32 because you're not.
That means you're not tied to the behavior of Win32, but to the behavior of WinRT. Its more than a subtle difference when it comes to legacy.
Member since:
2005-07-08
As a developer I really would like Windows Runtime to fully replace Win32, but only time will tell if this really happens.