3 ms·

There is actually nothing preventing anyone from writing a browser for windows on arm. The issue is that the API makes it inconvenient for existing browsers to

There is actually nothing preventing anyone from writing a browser for windows on arm. The issue is that the API makes it inconvenient for existing browsers to be ported. I've written a proof of concept HTML to WPF parser/renderer that worked fine inside WinRT. It wadls written in c# which is where the issue is I think...

joenathan 14y ago
Alternative browsers are allowed in the Metro interface, but not on the desktop in RT, that's what this article is about. Mozilla needs to be able to run binary code, and Microsoft has blocked all third party code from the desktop in RT.
josteink 14y ago
...WinRT. It wadls written in c# which is where the issue is I think... You can write WinRT in C++ as well. This was shown again and again on the Build Windows launch conference. Edit: I don't know how restricted the WinRT APIs are though and how being restricted to those (as opposed to the traditional Win32 APIs) affects what you can implement and not. Edit2: This post seems to answer it. Browsers will have issues. http://www.freelists.org/post/luajit/FYI-No-JIT-on-Windows-8-for-ARM http://www.freelists.org/post/luajit/FYI-No-JIT-on-Windows-8...
- jamesgeck0 14y ago
  Why is the ability to make code executable at runtime unavailable? JRuby can run in the browser, and NativeClient runs applications that use JIT[1], so I assume the ability isn't inherently at odds with sandboxing. 1. https://groups.google.com/forum/?fromgroups#!topic/native-client-discuss/karmYg8XACI https://groups.google.com/forum/?fromgroups#!topic/native-cl...