Linked by David Adams on Sun 14th Aug 2011 22:37 UTC
Google Google has released Chrome 14 to the Chrome beta testing channel, which includes, among other new features, the initial beta release of Google's "Native Client" technology, first announced in 2010 . . . Native Client is a set of open source tools that allow Chrome to run compiled C and C++ code the same way the browser currently runs JavaScript or other common web programming languages. Native Code offers both a security sandbox and a set of interfaces that provide C and C++ bindings to the capabilities of HTML5. That means web application developers will be able to tap into desktop libraries to create faster, more powerful web apps.
Thread beginning with comment 484983
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Hmmm ...
by panzi on Mon 15th Aug 2011 01:19 UTC in reply to "RE: Hmmm ..."
panzi
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.

Reply Parent Score: 5

RE[3]: Hmmm ...
by reduz on Mon 15th Aug 2011 06:42 in reply to "RE[2]: Hmmm ..."
reduz Member since:
2006-02-25

It's not that bad.. first, you can cross compile your stuff so it also runs on ARM (there's nacl for arm), second.. they are working on pnacl, which should be the same but instead pack an intermediate code that compiles to native on each platform..

Reply Parent Score: 2

RE[4]: Hmmm ...
by CapEnt on Mon 15th Aug 2011 12:15 in reply to "RE[3]: Hmmm ..."
CapEnt Member since:
2005-12-18

The real problem is that very few developers/companies will really care to compile and maintain code for architectures (and OSs) other than the most used one.

And the pnacl will be treated as the slow bastard cousin of the package, nothing more than a glorified javascript.

Reply Parent Score: 3

RE[3]: Hmmm ...
by Aragorn992 on Mon 15th Aug 2011 08:13 in reply to "RE[2]: Hmmm ..."
Aragorn992 Member since:
2007-05-27

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

Reply Parent Score: 1