3 ms·
I am curious to know if this also makes calls from WASM into JS faster. One of the issues with WASM is that you need the JS DOM API, it is essentially your OS
by Game_Ender 8y ago
I am curious to know if this also makes calls from WASM into JS faster. One of the issues with WASM is that you need the JS DOM API, it is essentially your OS abstraction layer, so faster that is, the better WASM will be.
- msoad 8y agoJS DOM API is a bridge to a native implementation. I wish we could use DOM directly in WS. Problem is DOM calls are blocking but removing the JS layer can help.
- bnjbvr 8y agoWe've had optimizations to make wasm -> JS calls fast for a long time, and they became even slightly faster (around 10 or 15%) last year. There is a proposal to add DOM integration within wasm, so one could import DOM functions in wasm and call them directly (from wasm to C++, without a "trampoline" in JS).