I read this article on arstechnica on Google's Native Client for Chrome, but I cannot understand what it is about. Can someone explain in layman terms what is the purpose of Chrome's Native Client?
migrated from webapps.stackexchange.com Aug 15 '11 at 11:16
This question came from our site for power users of web applications.
In very simple words:
In case of the native client, the code runs in the sandbox directly instead of the browser, hence reducing one layer below it. Because of this, the code execution will be faster
Note: This answer is not 100% accurate, but does explain the difference (or alteast most of it)
If the answer is wrong, please feel free to correct me
native client allows some c or c++ software to be recompiled to run inside chrome - this means applications that will run in chrome arn't restricted to flash or java .
They also support accelerated graphics (you could run doom or quake in it ;p) and multithreading. While the software runs at near native speeds, and as a native application, its sandboxed, so if something does go wrong, or its not a legitimate application, it won't affect the OS.
In short, its a way to run 'regular' software in browser.