4 ms·

There are a few things that WASM can do that JS can't (at least not now): - Memory management without GC - Unboxed data structures - SIMD - Shared-memory multi

• dagmx 6y ago
  I should clarify, in the context of the reply I was referring to security. Wasm is inherently as secure as JavaScript.
• hajile 6y ago
  Bytecode caching has been a browser feature for years[0] JS has atomics and shared memory arrays which also basically bypass garbage collection [1] JS had working simd.js implementations in both Firefox and Chrome until they were pulled in favor of WASM [0] https://v8.dev/blog/code-caching-for-devs https://v8.dev/blog/code-caching-for-devs [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... [2] https://github.com/tc39/ecmascript_simd https://github.com/tc39/ecmascript_simd https://blog.mozilla.org/javascript/2015/03/10/state-of-simd-js-performance-in-firefox/ https://blog.mozilla.org/javascript/2015/03/10/state-of-simd... https://01.org/blogs/2014/bringing-simd-javascript https://01.org/blogs/2014/bringing-simd-javascript