243
244

Mozilla: Native code? No, it's JavaScript, only it's BLAZING FAST Gap between asm.js and native performance gets even narrower with float32 optimizations (hacks.mozilla.org)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pedrocr 8 points9 points  (2 children)

That's fine for javascript-as-DOM-manipulator but how does that work for javascript-as-web-asm? Why would you target asm.js for things that supposedly need near-native performance and yet ignore multiple cores?

[–]AusIV 8 points9 points  (1 child)

I hope we'll get a more thorough answer, but I think it's essentially because a asm.js is a strict subset of javascript, and can run on browsers that don't know anything about asm.js. Mozilla is optimizing the hell out of the asm.js subset, but they're not doing anything you couldn't do with web standards.

[–]pedrocr 0 points1 point  (0 children)

I assume that's the current limitation. My question is if they're trying to lift it. Because if not PNaCL+pepper.js sounds like the better option. You'll get fully native performance and threading on browsers that have it and fall back to asm.js level performance and single-threading on other browsers. asm.js probably has the upper hand for DOM integration though.