> The slowness is not from the wasm runtime (which has been implemented standalone and is fast), but in the browser-y gui stuff
Not entirely true: In representative benchmarks, WASM has only 65% of the performance of native code. Of course, everything gets much worse the moment you interact with browser mechanics—WASM is only this fast while doing raw computations.
Not entirely true: In representative benchmarks, WASM has only 65% of the performance of native code. Of course, everything gets much worse the moment you interact with browser mechanics—WASM is only this fast while doing raw computations.
https://www.usenix.org/conference/atc19/presentation/jangda