Linked by Thom Holwerda on Fri 14th May 2010 18:28 UTC
Thread beginning with comment 424648
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.
RE[4]: Wall in the middle of the road spotted
by Neolander on Sat 15th May 2010 18:49
in reply to "RE[3]: Wall in the middle of the road spotted"
RE[5]: Wall in the middle of the road spotted
by umccullough on Sat 15th May 2010 19:27
in reply to "RE[4]: Wall in the middle of the road spotted"
but if it's just some glorified interpreter then why not ^^
It's not really an interpreter... not really.
Basically, it's a sandboxed environment that inspects the machine code of the NaCl app before allowing it to run, making sure it doesn't make any "dangerous" x86 calls that would allow it to affect other code or resources outside the sandbox. It is then allowed to run natively on the processor once it passes all the checks. It is allowed to link and call other NaCl libs, and is allowed to access host OS resources that the NaCl environment provides.





Member since:
2009-10-04
I really don't think you understand this... Right now, NaCl is just dependent on x86, which is what OSs like Haiku run on. And its APIs are so much smaller than Java, for example, that it would be much easier for an OS like Haiku to implement. And there would be no emulation layer like Wine.
PNaCl is just as platform independent as Java or Python. In fact, it's probably even easier for an OS like Haiku to implement because the APIs are much smaller.