For many of these, WebAssembly is critical to either their entire product or a major feature.
But I think this alone is not very convincing. We don’t yet see major websites entirely built with webassembly-based frameworks.
Why should it be necessary to build things only in wasm for the web? JS is a really good language for building frontends. There is a reason why lots of companies prefer building native applications with React. People always complain about framework bloat with JS, but then we want to hype up shipping huge wasm binaries? Just for basic interaction in a UI?
Wasm is doing great, inside and outside the browser. But it won’t replace JS because there’s no reason to do so.
JS is a really good language for building frontends.
Disagree. I think there is an entire ecosystem built out of coping with it being an awful language. That being said, the ecosystem is pretty good at adding first class features to a third rate language and your points stand. I don’t want anything to do with JS in the back end, though NodeJS isn’t entirely awful.
Why should it be necessary to build things only in wasm for the web? JS is a really good language for building frontends. There is a reason why lots of companies prefer building native applications with React. People always complain about framework bloat with JS, but then we want to hype up shipping huge wasm binaries? Just for basic interaction in a UI?
Wasm is doing great, inside and outside the browser. But it won’t replace JS because there’s no reason to do so.
I agree with your gist but…
Disagree. I think there is an entire ecosystem built out of coping with it being an awful language. That being said, the ecosystem is pretty good at adding first class features to a third rate language and your points stand. I don’t want anything to do with JS in the back end, though NodeJS isn’t entirely awful.