2 ms·
But is this how it is implemented by actual browsers? if memory serves v8 is pretty much reusing most of JS VM for WASM?
by qaq 9y ago
But is this how it is implemented by actual browsers? if memory serves v8 is pretty much reusing most of JS VM for WASM?
- exDM69 9y agoYes, the browsers do share parts of their JavaScript execution engine with WASM. Which makes sense because WASM still needs to interact with JS. That doesn't mean it can't be fast or start quickly (or at least quicker than asm.js). From the developer's point of view that doesn't matter. You're delivering WASM and not C or JS code over to the clients.
- marcosdumay 9y agoWASM requires a much simpler VM than JS. It doesn't take most of a JS VM.