3 ms·
I might be wrong but I think you can conceptualize like this... Wasm is essentially a target bytecode and runtime based on the well tread security model of jav
by jayd16 4y ago
I might be wrong but I think you can conceptualize like this...
Wasm is essentially a target bytecode and runtime based on the well tread security model of javascript in the browser.
Browsers can run it, languages can compile to it, apps of any language can host a runtime that runs it. This leads to infinite permutations and nesting of concepts.
Because its web tech there's a dozen ways to do the same thing.
- test6554 4y agoYep. That's my take. The vision is that you write code in any language you like. You compile (transpile?) it down to efficient low-level JS (WASM), run in the browser as if you wrote JS code. I have zero experience with it, but I think I get it and it's neat. I'm a little curious about what working with the DOM is like in C# > WASM or Rust > WASM. I pitty the foo who had to code that... and will we get non-breaking, more efficient native DOM manipulation at some point?
- MuffinFlavored 4y agohttps://stackoverflow.com/questions/59708546/access-the-dom-in-webassembly https://stackoverflow.com/questions/59708546/access-the-dom-...
- Garlef 4y agoWASM is not low level JS There was a "predecessor" project (Asm.js) that would output low level JS, though. https://stackoverflow.com/questions/31502563/what-is-the-difference-between-asm-js-and-webassembly https://stackoverflow.com/questions/31502563/what-is-the-dif...