4 ms·

Or just not use JS for serious computation. It was never designed for this, and upgrading the core language to do serious computation will be like putting lips

by opless 11y ago

Or just not use JS for serious computation. It was never designed for this, and upgrading the core language to do serious computation will be like putting lipstick on a pig or a sticking plaster on a wooden leg. You're correct though Emscripten and WebGL are amazing things, but ultimately hacks. With browsers scurrying to implement ASM.js support, JITs etc... (because most JS developers write shonky code and interpreting JS is not fashionable any more) JS considered dangerous. DO. NOT. USE.

opless 11y ago
Also the web always was "write once, suck everywhere" since its inception too. It was never meant to be a layout markup language, we already had SGML for that.
- pcwalton 11y ago
  SGML doesn't have layout at all!
  - opless 11y ago
    My mistake, I may have been misremembering DSSSL
pcwalton 11y ago
> most JS developers write shonky code and interpreting JS is not fashionable any more Interpreting JS is so "fashionable" that most browsers (all but Chrome/V8) keep around their interpreter, and most code runs in it. That's because, contrary to popular belief, most JavaScript code is cold and not performance critical.
- opless 11y ago
  While I agree with the fact that most JS is not performance critical (which was kinda my point) I'm interested in where these interpreters are, as Mozilla has had a JIT for ages (for example) ... if they kept their interpreters about surely it would be just for non-jit compilation targets?