See, that's the problem. As long as WASM is not able to pull its own weight and needs JavaScript to provide the spine it will languish in a niche or two.
Ultimately someone will decide that supporting two different languages and ecosystems is too expensive and not worth the marginal advantage and it will go back to JavaScript only.
We've been there and we have done that with Java applets.
The ease of interoperation with the host language (JS in this case) is a benefit, not a problem. WASM (without the WASI stuff) is fundamentally a portable assembler target, something that other languages can target, and all the baggage of browser and OS APIs can stay in the host environment and be selectively exposed to the WASM runtime. This makes WASM truly portable (again, without the WASI stuff).
nah, web developers that aren't doing simple CRUD are using interesting libraries powered by wasm without even care that it's powered by wasm: opencv, sqlite, duckdb, imagemagick, ffmpeg, ... anything AI/using GPU: tensorflowjs.
Those libraries are not something will be able to be JS only anytime soon, and no, Java applets has never allowed us to use C/C++ libraries on the web before.
Come up with great interface for web apps in WASM and the world will follow. Eventually browsers can just implement your interface directly without the javascript glue.
See, that's the problem. As long as WASM is not able to pull its own weight and needs JavaScript to provide the spine it will languish in a niche or two. Ultimately someone will decide that supporting two different languages and ecosystems is too expensive and not worth the marginal advantage and it will go back to JavaScript only.
We've been there and we have done that with Java applets.