Wednesday, May 12th, 2010
The Native Client SDK preview, in contrast, includes just the basics you need to get started writing an app in minutes: a GCC-based compiler for creating x86-32 or x86-64 binaries from C or C++ source code, ports of popular open source projects like zlib, Lua, and libjpeg, and a few samples that will help you get you started developing with the NPAPI Pepper Extensions. Taken together, the SDK lets you write C/C++ code that works seamlessly in Chromium and gives you access to powerful APIs to build your web app.
Salt and Pepper indeed. A friend at a browser vendor was looking into Pepper and thought that the specs were definitely….. thorough shall we say? Take Pepper Audio by itself. A bit of a beast! :)
It is interesting to watch Google give C/C++ developers (and legacy code) a different path to the Web (beyond NPAPI and… ActiveX!). You can imagine this being increasingly important when you think about Chrome OS.
Ideally, the Web platform itself evolves fast enough that this project is always an onramp for legacy code…. what do you think?
@hbridge has an interesting view:
Pepper is very much a work in progress and we expect it to change — that’s why this is a preview! Feedback welcome :)
ActiveX was designed to provide unrestricted access to native APIs so it wound up being a security nightmare.
NaCl is designed to give access to native code performance, but only to APIs similar to what JS offers, so security model is same.
Posted by Dion Almaer at 1:12 pm