Linked by Thom Holwerda on Fri 14th May 2010 18:28 UTC
Permalink for comment 424823
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2010-03-08
Yes, but since NaCl takes care of the loading job and since NaCl and its libraries take care of the system calls, we end up using an interpreter-like behavior : code cannot run directly on the computer and must be analyzed and translated to native code by an external program.
PNaCl code cannot just be loaded by the OS and handed to the processor with a "good luck !". It's some kind of bytecode that must be translated to something the local architecture and the local OS understand prior execution, just like in Java apps.
However, we all know about Java's startup performance. It's an inherent drawback of AOT compilation. So I suppose Google have something behind their back if they want to put this sodium chloride thing everywhere on the web. Maybe some kind of cloud compilation services ?
Edited 2010-05-16 07:28 UTC