News for hackers. Stuff that matters.
Re:Chromium Blog: A sneak peek at the Native Client SDK by JeffJenkins on Wednesday May 12, 2010 @12:41PM (#1341434)
To what degree does "Embrace and Extend" apply to what Google is doing?
Re:Chromium Blog: A sneak peek at the Native Client SDK by stuntmouse on Wednesday May 12, 2010 @01:12PM (#1341543)
That's pretty vague. How does it apply to this situation?

The code is open; part of the NaCL API is designed around Posix/Linux; the Plugin API is the familiar NPAPI and its extensions.

Which part is proprietary or controlled by Google?

To my mind, some more relevant questions are: Does this tie the web to x86 (and ARM)? Can it be adapted securely to x86-64? Can it be made secure? Can multiple implementations be made secure?

Re:Chromium Blog: A sneak peek at the Native Client SDK by papachito on Wednesday May 12, 2010 @05:12PM (#1342286)
> Can it be adapted securely to x86-64?

FTA: "a GCC-based compiler for creating x86-32 or x86-64 binaries from C or C++ source code"