Linked by David Adams on Sun 14th Aug 2011 22:37 UTC
Thread beginning with comment 484983
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Also it is architecture dependent
Huh? Not according to Ars:
The original implementation of NaCl suffered from some major technical problems that seemed difficult to overcome. In particular, the sandboxing mechanism relied on certain characteristics of the x86 architecture. That issue has since been addressed; it now has 64-bit support and experimental ARM compatibility.
Ah but probably I have misunderstood. I guess developers will compile for a specific architecture before distribution?
Edited 2011-08-15 08:14 UTC




Member since:
2006-01-22
Also it is architecture dependent, so even worse than flash! It will only work for one CPU architecture, so if it's compiled for x86 it won't run on your ARM handheld or the yet unknown computer architecture of the future. Also can you get a "a script on this site makes your browser slow. quit the script?" for NaCl? I'd doubt that. After all you can use threads in it. So one could spawn hundreds of threads all doing "while(1);" thus DoSing the client computer.
It would be a better move to invent a new statically typed language for the web that can be properly JITed and optimized. WebGo? But still, someone has to convince me that we really need this.