Oi. No. To say that WASM and JS run in the same VM is utterly misleading the the point of being wrong. They are not 'The Same VM'. They are 'Different VMs'.

Oi. No. To say that WASM and JS run in the same VM is utterly misleading the the point of being wrong. They are not 'The Same VM'. They are 'Different VMs'. That in the case of Chrome and Firefox they happen to executed 'Side By Side' is relevant, but they are not the same vm. "Because it runs on the same VM, it's as stable as JavaScript, which is extremely stable at this point" This is a 'double down' on the fallacy that 'They are the same VM'. "It's effectively instantaneous simply because it's using the same engine as JavaScript, which is already loaded." First, so you're not going to count the startup time of the 'Engine' in the 'startup time'? But somehow that 'startup time' would be counted for example in JVM startup? That wouldn't be a useful comparison, wouldn't it? If you make a WASM-based app, you're going to have to throw in 'net startup time'. Second, aside form the issue of 'Engine' startup time, you have to consider how quickly the code gets going. It is not 'instantly', nothing is instant in a VM, notably WASM has to 'compile' - not unlike Java bytecode. Java, JS and WASM all have different profiles here. JS is 'very fast' to start, because that's why it's optimized. Java is slower to start but after about 1000 iteratons of a block of code, 'runtime profiling' makes it fast. Often faster than humans could code in C++. WASM is slow to compile, and currently has little in the way of optimization. Slow to start, slow to compute. "Because LLVM targets wasm, you've got many many languages that are supported." I'm guessing you're not a developer, and have never used WASM? You do realize you can run JS in Java? Or Java in JS? Or Rust on Java? But that would mostly be stupid and pointless in any real world environment, which is why nobody does it? Which is why nobody runs Java, C#, Python, Elixir in WASM for anything other than a mockup experiment. So no, my points are all valid. Today, WASM is the domain of Emscripten and maybe some Rust experiments, and that's that. It's slow, cumbersome, nobody is really invested in it. Maybe someday, but it's not on the horizon just yet.