WASM provides a compilation target for languages, enabling them to be compiled such as to be executable inside the browser.
Of course, it's lacking certain features currently - such as direct DOM access from WASM and initializing a binary without using JavaScript.
Ignoring that, the goal of a browser-compatible compile target is satisfied by JavaScript today. However, the output JavaScript will often be convoluted due to it being a high level language itself and often result in an output larger than the source code itself.
Assuming a world where DOM access existed inside wasm, would:
- Excluding the language runtime, would JavaScript or TypeScript compiled to WASM result in binary sizes smaller than the equivalent JavaScript bundle generated using Webpack?
- Will runtimes be shared and delivered separately? See Java, SilverLight, Flash, Shockwave