Somewhat dubious claim if it was right or not, the only benefit was that asm.js was backwards compatible and set the stage for Mozilla to lose out by simply having the slower JS engine whereas NaCL/PNaCL proposal was "performance neutral" between browsers.
For what, Firefox is for all practical purposes irrelevant in a Chrome dominated Web, Google can steer WebAssembly into whatever direction fits Chrome.
Somewhat dubious claim if it was right or not, the only benefit was that asm.js was backwards compatible and set the stage for Mozilla to lose out by simply having the slower JS engine whereas NaCL/PNaCL proposal was "performance neutral" between browsers.
For what, Firefox is for all practical purposes irrelevant in a Chrome dominated Web, Google can steer WebAssembly into whatever direction fits Chrome.
That's the situation today, but in 2013 when asm.js was invented Firefox was still relevant.
Yes, and the question in retrospective is was it worth it?
2 replies →