wasm is not bound to javascript in any meaningful sense
So when people say stuff like "high-performance latency-sensitive use cases are applicable to wasm" they clearly only understand performance and latency in comparison to Javascript.
and like there's plenty of people doing wasm on the server where performance is measured in microseconds
According to the website and the core spec it's still the main goal
> there's plenty of people doing wasm on the server where performance is measured in microseconds
I'm old enough to remember when node.js was also marketed as "web scale" and high performance.