4 ms·
Google is already heading there with native client. They're changing the approach to serving up LLVM bytecode on the server, which is translated to x86 or ARM
by hannibalhorn 16y ago
Google is already heading there with native client. They're changing the approach to serving up LLVM bytecode on the server, which is translated to x86 or ARM by the browser prior to execution. For future apps that require performance, it should work well and with Google's weight behind the tech I think it'll be widely adopted.
There's already a version of python that runs in native client, and pretty much anything could conceivably be ported.
- AndrewDucker 16y agoOooh, LLVM bytecode. I hadn't thought of that, but it's a perfect choice! I hope it does get picked up by other people.
- tav 16y agohttp://nativeclient.googlecode.com/svn/data/site/pnacl.pdf http://nativeclient.googlecode.com/svn/data/site/pnacl.pdf ^ Overview of the LLVM-based Portable Native Client (PNaCl) architecture.
- TorKlingberg 16y agoHow do you get it properly sandboxed, while still able to interact with the browser document model?
- stcredzero 16y agoLimiting the translation and also through binary inspection. That's kinda the whole point of NaCl!