3 ms·
> Add Mozzilla to the mix, for not wanting to adopt PNaCl. Mozilla wasn't in any position to command the market, even at the time PNaCl was created. PNaCl fail
by Ygg2 2y ago
> Add Mozzilla to the mix, for not wanting to adopt PNaCl.
Mozilla wasn't in any position to command the market, even at the time PNaCl was created. PNaCl failed on its own demerits.
> Firefox is almost irrelevant now
Firefox has been irrelevant because it doesn't have the trillion dollar budget of Apple and Google, nor the vendor lock-in, and with that no reach which would enable it to steer web the way it deems fit. It has nothing to do with asm.js
- pjmlp 2y agoNot at all, had Mozilla adopted PNaCL instead of coming up with asm.js, and WebAssembly would never come up, delaying everything for a decade. Here is a memory refresher from 2011, "Mozilla's Rejection of NativeClient Hurts the Open Web" https://chadaustin.me/2011/01/mozillas-rejection-of-nativeclient-hurts-the-open-web/ https://chadaustin.me/2011/01/mozillas-rejection-of-nativecl...
- Ygg2 2y agoMozilla wasn't the only one with problem with PNaCl. They were definitely most opposed to it, but even Opera was strongly against it (granted it was around 2011).
- the_why_of_y 2y agoThe argument against NaCL was that it was the browser API, PPAPI, was poorly documented and exposing implementation details of Blink/Chromium and thus very difficult to implement in a non-Chromium browser, so it's no surprise that Mozilla, Apple, and Opera were unenthused. https://bugzilla.mozilla.org/show_bug.cgi?id=729481#c83 https://bugzilla.mozilla.org/show_bug.cgi?id=729481#c83