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 510423
To read all comments associated with this story, please click here.
Already failed strategy
by siki_miki on Tue 13th Mar 2012 17:17 UTC
siki_miki
Member since:
2006-01-17

MS should have built WinRT as a complete replacement for the aged and ugly 90's Win32. Just how Apple did it with OS X API's and supported legacy ones for a while (until the 64 bit transition, that is). That would ease development for everyone, regardless of language and whether it is managed or native code.

With WinRT being useful only on Metro, they want to push their troubled and flawed interface, but I can already imagine how this is going to work out with PC crowd - it won't, it will fail spectacularly. All that is another manager (Ballmer) decision that doesn't have much sense, except that MS is comfortable enough on the desktop to go ahead with it trying to make a foothold in the market.

The locked down Metro for Windows doesn't have any sense on PC's, at least without the non-default option to disable signing check. It will be jailbroken and most people will run that, or otherwise completely ignored by devs. Really no need to pretend to be Apple.

Reply Score: 2