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 510307
To read all comments associated with this story, please click here.
Member since:

I am aware of it, but what I meant is that Microsoft would do better by fully supporting WinRT for the desktop and forgeting this Metro nonsense.

I do have Windows 8 + MSVC 2011 installed, and also
do Windows development, so I am quite aware how Windows 8 is shaping up.

Why should the 'forget this metro nonsense' given that it will be the native API that Windows Phone developers have been clambering for - where you have an API that spans from the tablet to the phone. The two are going to co-exist together with Windows - this idea of the desktop being akin to classic on the Mac (a prior article posted on is quite frankly a persons flight of fancy rather than what reality is actually like. Microsoft may do some stupid things at times but I doubt they're going to throw their bread and butter (enterprise customers) under the bus with a idea such as Metro replacing the desktop long term given that it simply doesn't scale when it comes to large and complex applications such as Visual Studio or even Microsoft Office for that matter.

Edited 2012-03-12 16:21 UTC

Reply Parent Score: 2