5 ms·
Great article. I applaud the massive amount of effort that's resulted in JS being far faster than anyone ever expected. It's time to switch to WASM though. Hal
by nullwasamistake 7y ago
Great article. I applaud the massive amount of effort that's resulted in JS being far faster than anyone ever expected.
It's time to switch to WASM though. Half native speed with almost no parsing overhead. As integration and tooling improve I see no reason to stick with JS.
It also rectifies a number of historical mistakes that are nearly impossible to fix. Mainly threading. WebWorkers etc are a huge hack. No atomic data structures, no shared memory, huge overhead. WASM will be many times faster than JS from threads alone. Add the natural speed advantage and you're looking at maybe a 20x performance difference.
- xenospn 7y agoThe last milestone I see on the WASM page is from 2017 - is it still a thing?
- nullwasamistake 7y agoIt's stable now and implemented in all major browsers.
- Siwka 7y agoLast time I checked you didn't get DOM manipulation, so you'd still need to use JS for that.
- nullwasamistake 7y agoYes. Rustaceans have stepped up and provided a ton of nice shim layers though. So practically, you don't have to actually write your own js to interface