On Sun, Aug 14, 2011 at 10:29 AM, Marco Leise <marco.le...@gmx.de> wrote:
> Am 14.08.2011, 06:41 Uhr, schrieb Andrew Wiley <wiley.andre...@gmail.com>: > > On Sat, Aug 13, 2011 at 5:10 AM, bearophile <bearophileh...@lycos.com>** >> wrote: >> >> Found though Reddit. It seems Chrome is starting to warm up to the Native >>> Client (NaCl) idea, the Chrome Beta now has a working NaCl: >>> >>> http://chrome.blogspot.com/**2011/08/building-better-web-** >>> apps-with-new.html<http://chrome.blogspot.com/2011/08/building-better-web-apps-with-new.html> >>> >>> >>> http://channel9.msdn.com/**Shows/C9-GoingNative/** >>> GoingNative-0-Help-us-fly-**this-plane-Some-modern-C-Meet-**Ale-Contenti<http://channel9.msdn.com/Shows/C9-GoingNative/GoingNative-0-Help-us-fly-this-plane-Some-modern-C-Meet-Ale-Contenti> >>> >>> It's one (the only?) chance to use D in the browser. >>> >>> Bye, >>> bearophile >>> >>> >> Just thought I'd point out that the previous discussions on NaCl seem to >> have missed this part of the overview: >> "The Pepper Plug-in API (PPAPI), called *Pepper* for convenience, is >> included in the Native Client SDK. This library is written in C, and the >> SDK >> also provides a set of C++ bindings for it. Native Client modules use the >> Pepper API to communicate with the browser's JavaScript, the DOM, and >> other >> resources managed by the browser. The Pepper Library also provides a >> platform-independent multimedia API that Native Client modules can use for >> audio, video, and 2D graphics." >> >> So yes, this is somewhat geared toward multimedia, but it looks like it >> can >> also replace javascript in web apps. >> > > Is this basically the same as the Java applet interface to the browser > without the "compile once, run everywhere", but with better API? > I haven't ever dealt with the applet interface, but that quote came from http://code.google.com/chrome/nativeclient/docs/technical_overview.html if you want to take a closer look. The Pepper API docs are there as well.