Linked by Thom Holwerda on Sun 11th Mar 2012 22:21 UTC
Permalink for comment 510280
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2007-09-08
Not being able to have a JIT (it's technically possible, but applications that do it would fail validation) is, by itself, enough to prevent any modern web browser from being a native Metro application.
That's not even considering everything else. It would require a massive effort to move everything over to WinRT. It wouldn't gain you anything. The new WinRT APIs are still accessible from a hybrid WinRT / Win32 application. The replacement APIs, like networking, don't actually offer any extra features over the existing Win32 APIs.
Besides, the architecture of Windows 8 requires that the Metro web browser be a hybrid application. That's just the way it works. The Metro web browser is determined by whatever the default desktop browser is. That's why, if you install Firefox on Windows 8 and set it as the default browser, the Metro version of IE 10 disappears.