4 ms·
> Someone has to do Javascript though: targeting the web browser client is important and here to stay although it is evolving, and wasm is part of that evolutio
by StavrosK 9y ago
> Someone has to do Javascript though: targeting the web browser client is important and here to stay although it is evolving, and wasm is part of that evolution.
WebAssembly has nothing to do with Javascript, though. I don't think that's what the GP means.
- SideburnsOfDoom 9y ago> WebAssembly has nothing to do with Javascript They are different VMs in the browser alongside each other, I was wrong about that (1) However, this comment says more about the ways that they are and aren't equivalent (2) Both are for "targeting the web browser client" so they have that in common, and a lot of the logic about their place in the world is therefore the same for both of them. 1) https://github.com/WebAssembly/design/issues/219 https://github.com/WebAssembly/design/issues/219 2) https://news.ycombinator.com/item?id=15982036 https://news.ycombinator.com/item?id=15982036
- steveklabnik 9y ago> They are different VMs in the browser alongside each other My understanding is that this is not true; wasm is more of a particular mode or API of interacting with the existing JS VM rather than having its own. You want to re-use the JIT, etc, for wasm. Note that that issue is from 2015. That said I don't work on these implementations so maybe I'm wrong as well.