8 ms·
Right, because wasm is there to solve all our performance problems, isn't it? And how exactly is your jquery.wasm going to access the DOM? Or expose methods to
by sjrd 9y ago
Right, because wasm is there to solve all our performance problems, isn't it?
And how exactly is your jquery.wasm going to access the DOM? Or expose methods to your application, for that matter?
wasm is not a drop-in replacement for JS.
- Spivak 9y agoNo, but if we're being honest, it's exactly what everyone wants it to be. A bytecode for the web.
- Fifer82 9y agoI really don't know much about wasm. I just wondered though, from a birds eye view, does using wasm effectively give you control of everything within the "frame" of your browser? Can I get rid of the DOM(boilerplate aside), get rid of CSS? For example HTMLCanvasElement is a flat surface. I can do what I want within it as a scene graph renderer. Could I do that with wasm? Could I invent my own 2D entities (x, y, width, height). My own 2D Constraints resize like Apple Devices etc?
- skybrian 9y agoIt's still in the same sandbox as JavaScript. You don't get any new API's. There's only going to be speedup on CPU-intensive things.
- markdog12 9y agoThere are plans for WebAssembly modules to directly access the DOM: https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md#host-types https://github.com/WebAssembly/gc/blob/master/proposals/gc/O...
- adamnemecek 9y agoEventually the Dom might be replaced with some webgl renderer.
- flavio81 9y ago> wasm is not a drop-in replacement for JS It is not a "drop-in" replacement in any way, but I'm pretty sure it will eventually replace JS completely.