4 ms·
We may need to ask some hard questions like: do browsers really need wasm in the first place?
by postepowanieadm 1y ago
We may need to ask some hard questions like: do browsers really need wasm in the first place?
- AndyKelley 1y agoI would ask the question the other way around: do browsers really need JavaScript? It's a lot easier to maintain a WebAssembly engine than a JavaScript engine.
- hardwaresofton 1y agoReally interesting to hear you say that — Thanks for the WASM impl in Zig! On the do-browsers-need-js point, you might be interested in: https://github.com/wasi-gfx/webidl2wit https://github.com/wasi-gfx/webidl2wit
- melodyogonna 1y agoWASM came about as a result of demand, not because people had too much free time. Browsers were being used for more complex things, which resulted in companies adopting hacky solutions to enable more performance. WASM is seeking to develop a consistent standard for these use cases.
- nasso_dev 1y agoiirc WASM bytecode closely resembles V8 IR. If you're writing a JS engine, might as well provide a more direct frontend to it... I don't think it adds much.