3 ms·
First of all, NaCl is now Pepper-only, so it is no longer compatible with Firefox. Firefox uses the NPAPI, not the Pepper API. Pepper is itself an instance of G
by ootachi 15y ago
First of all, NaCl is now Pepper-only, so it is no longer compatible with Firefox. Firefox uses the NPAPI, not the Pepper API. Pepper is itself an instance of Google not showing interest in working with the other browser manufacturers. The other browser manufacturers considered it unnecessary to add two incompatible plugin APIs when the NPAPI already exists and could just be extended.
Second, the position of every other browser manufacturer is that NaCl is undesirable because (a) it's not compatible with JavaScript, so it requires another language runtime and (b) that it locks the Web into x86 and ARM. As bzbarsky of Mozilla posted here [1], if Google had made and pushed NaCl a decade ago, the iPhone would be unable to browse the web. Google ignored the other browser manufacturers' concerns and are now pushing NaCl to gain a competitive advantage.
[1]: http://news.ycombinator.com/item?id=3391747 http://news.ycombinator.com/item?id=3391747
- nkassis 15y agoI appreciate your reply. As far as the Pepper API my understanding is that it was an extension to NPAPI to improve it, not an attempt at creating an incompatible API. I can't find any source on why Mozilla decided to not use it. From the Pepper wikipedia page it looks like some of the goal of Pepper would be very useful to every browser.