3 ms·
Not only that, a few months after asm.js was included in Firefox, Chrome had optimizations done that helped a great bit with asm.js (http://blog.chromium.org/20
by hyperpape 13y ago
Not only that, a few months after asm.js was included in Firefox, Chrome had optimizations done that helped a great bit with asm.js (http://blog.chromium.org/2013/05/chrome-28-beta-more-immersive-web.html http://blog.chromium.org/2013/05/chrome-28-beta-more-immersi...). Possibly a coincidence, but they certainly seem to care about asm.js performance above and beyond generic JS performance, even if they're not going to support the pragma.
- magicalist 13y ago> but they certainly seem to care about asm.js performance above and beyond generic JS performance That doesn't follow. They certainly care about it; it's now in the Octane benchmark suite, which means they think it's representative of code that should be optimized for, but it's only part of the suite, which means it's just one more style of code that should be able to run efficiently in a modern JS engine.
- Alphasite_ 13y agoYou're oth saying the same thing for the most part, I dont think he's trying to imply that its their focus, just that its important enough to optimise specifically.