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