Looks like you're getting down voted, but the folks at Mozilla seem like they agree and are working towards making WASM more first class in the browser: https://hacks.mozilla.org/2026/02/making-webassembly-a-first...

That's specifically about string-marshalling overhead, which is only a problem when trying to talk to the DOM from the WASM side (which arguably is a silly idea to begin with, but to each their own I guess).