> And in fact running anything else than "C languages" in WASM is at least as inefficient as running "C languages" on the JVM… Hell, it is a really safe bet to

> And in fact running anything else than "C languages" in WASM is at least as inefficient as running "C languages" on the JVM… Hell, it is a really safe bet to say that running a C-like program on the JVM is much much faster than porting a whole runtime (which is very performance-oriented) on top of a runtime and make it run some code. Wasm simply can’t expose the optimizations runtimes routinely make use of (template interpreters for example))