logoalt Hacker News

pmontralast Friday at 1:46 PM1 replyview on HN

About building web apps:

> It could be the continued lack of DOM bindings that have been considered a key missing piece for several years now, or maybe something else or more fundamental.

More fundamentally, every front end developer uses more or less the same JS language (Typescript included) and every module is more or less interoperable. As WASM is a compilation target, every developer could be using a different language and different tools and libraries. One of them could have reached critical mass but there is a huge incumbent (JS) that shadows everything else. So special purpose parts of web apps can be written in one of those other languages but there still is a JS front end between them and the user and GUIs can be huge apps. It looks like a system targeted to optimizations.

And for the backend, if one writes Rust or any other compiled language that can target WASM, why compiling to WASM and not to native code?


Replies

CuriouslyClast Friday at 2:15 PM

Using WASM lets you bundle native stuff in NPM packages without cross compiling.