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.