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 510427
To read all comments associated with this story, please click here.
RE: Already failed strategy
by Alfman on Tue 13th Mar 2012 18:04 UTC in reply to "Already failed strategy"
Alfman
Member since:
2011-01-28

siki_miki,

I agree that WinRT programming should not be dependent on using the metro interface, and that such a limitation is entirely artificial. A "write once, run anywhere" philosophy has delivered tremendous benefit to users and devs alike over the years. There's no technical reason WinRT apps couldn't be run on a WIMP desktop with a keyboard and mouse and be just useful as running fullscreen in Metro. Users would benefit from being able to choose where they want to run their apps.

However MS doesn't want to risk having users who prefer to run their WinRT apps on the desktop rather than in Metro. So MS decided the best thing to do was to ban that possibility from the get-go. The ultimate goal is to rope all Win8 users into using metro and make everything else a jarring experience.

Edited 2012-03-13 18:08 UTC

Reply Parent Score: 2