Linked by Thom Holwerda on Sun 11th Mar 2012 22:21 UTC
Windows And thus, Microsoft bites itself in its behind with Metro. As you all surely know by now, the Metro environment in Windows 8, and its accompanying applications, need to follow a relatively strict set of rules and regulations, much like, say, applications on iOS. For one type of application, Metro has already proven to be too restrictive and limited: web browsers. Microsoft has had to define a separate application class [.docx] - aside from Metro and desktop applications - just to make third party web browsers possible for Windows 8.
Permalink for comment 510277
To read all comments associated with this story, please click here.
kaiwai
Member since:
2005-07-06

Personally I think the best would be to allow WinRT to be fully used for desktop applications and give legacy status to Win32.

Metro will most likely suffer the same fate as Vista on the desktop.


From what I have read WinRT isn't a complete replacement for win32 yet and it is possible to create desktop applications using WinRT. The post I read a while back:

http://social.msdn.microsoft.com/Forums/en-US/winappswithnativecode...

Parts of the WinRT will be tied directly to metro such as certain XAML functions only make sense in a Metro environment however I'd say the enterprise preview will probably include more details being released and Windows 9 being the release where WinRT becomes a top to bottom replacement for Win32. Microsoft has a lot on its plate right now so one can only guess that they focused on WinRT for Metro because it is the most urgent as it addresses the tablet and the demand for a native API that many Windows Phone developers have been asking for.

Reply Parent Score: 1