Hacker News Reader

> But for certain high-performance latency-sensitive use cases like trying to deliver feature flags globally to mobile apps, or web apps around the world (that is our use case)… it’s definitely very applicable to this problem.

I fail to see how it's applicable. Unless your entire world is Javascript and its performance

View on HN

wasm is not bound to javascript in any meaningful sense

wasm literally came out of asm.js and browsers. And its original goal is literally to make stuff in browsers more performant compared to Javascript.

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.

it started there but that's not like the only goal of the thing

and like there's plenty of people doing wasm on the server where performance is measured in microseconds

> it started there but that's not like the only goal of the thing

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.

Reply on news.ycombinator.com