For existing code bases that don’t already do DOM manipulation (so, all of them) other parts of the Web API might be more useful, like the canvas, the video API, the RTC API etc.

The issue in general is how to bridge these JS OOP APIs to something that's basically assembler.

If WASM gains a foreign object model calling convention or whatever, we're in game.

Wasm is not basically assembler, it's (going to be) very high level:

- https://github.com/WebAssembly/reference-types

- https://github.com/webassembly/threads

- https://github.com/WebAssembly/exception-handling

- https://github.com/WebAssembly/function-references

- https://github.com/WebAssembly/gc

Though it is true that the original MVP was very barebone and could be compared to assembler. However, the reference types proposal has been shipped in all major browsers and is considered "finished".