3 ms·
I can't be the only one who doesn't think this is cool. From an application security point of view, PNaCl -- and the general trend of packing everything into b
by eliteraspberrie 13y ago
I can't be the only one who doesn't think this is cool.
From an application security point of view, PNaCl -- and the general trend of packing everything into browsers -- is not good. The first rule of security is to keep things small and simple. A browser with a built-in compiler is no longer a browser.
If Google had its way, phones would just be dumb bootloaders for operating systems downloaded on the fly from their cloud.
- eliben 13y agoDo note that PNaCl uses Native Client as a base. Native Client is a very secure sandbox that's been out in the wild for some time, had security contests run against it and has in general proven itself to be very secure. The PNaCl translator (backend of the compiler) runs within a NaCl sandbox itself, so nothing in the Native Client security model is compromised.
- _random_ 13y agoSo JS shouldn't be JIT-ed as well?
- enneff 13y agoYou have it backwards. The PNaCl thing actually makes it more realistic to actually install a "Web App" inside Chrome and use it independent of an internet connection. The browser is lagging well behind Android and iOS in terms of user experience. Efforts like PNaCl and asm.js help to restore the balance. All browsers include compilers already, by the way.