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 510270
To read all comments associated with this story, please click here.
RE: I think
by Moochman on Sun 11th Mar 2012 23:46 UTC in reply to "I think"
Member since:

For example, what incentive do Firefox devs have now to use the WinRT's new asynchronous networking APIs to deliver optimal performance and reliability? Now they are not usage aware (Can't tell when the PC is on metered or data capped mobile broadband, as one example).

Does IE10 make any actual use of this usage-awareness?

You want to talk jarring? Downloading setup.exe from Firefox's website, being thrown to Desktop Mode, to install a Browser, make it the default, only to get it's Metro Style counter part. That's f--king jarring.

Well, if it turns out it's not allowed in the Windows Store and requires desktop switching you should blame Microsoft for that, not Mozilla....

Which is why I view this as a stop gap, and I am hopeful that Firefox devs will eventually transition to a more streamlined approach.

I fully expect them to, since as a browser they surely won't want to be barred from Windows on ARM. Whether Windows on ARM will be worth it to the likes of Adobe, Avid or Autodesk... I kind of doubt it.

Edited 2012-03-11 23:58 UTC

Reply Parent Score: 4