It won't, and shouldn't. Wasm meets very few of it's goals, and is nowhere near any native speeds under real world workloads. Even speedups with SIMD ar hindered, and the entire design and implementation of it in the clang/llvm compiler is very experimental.

Go work with wasm in the browser, you will pull your hair out at the fact emscripten is still the most used tool. It's all very hackey and if something breaks, you wont fix it.

I have worked with wasm in the browser in production. Yes, there are many issues, yes I have some critiques of the multithreading proposal, but in the long run portable workers solve lock-in.

WASM adoption is not something everyone agrees is a great thing in the context of physical CPUs.

100% this. Cross-platform binaries that "just work" everywhere in a hardware agnostic manner is going to be huge.

Browser-based games and real-time 3D applications are the one's I'm most excited about, personally but that may be because I'm developing a WASM startup in this space.

They should think of a new slogan, maybe "Write once, run anywhere". Yea that sounds good.

WASM runs on 3 billion devices!

It was a joke on the Java installer saying Java runs on 3 billion devices for ages, not sure if you got it or not.

Pascal P-Code.