[_m1x6]

The real issue is that you cannot access the DOM via WASM.

Also the previous article is here[0].

[0]: https://news.ycombinator.com/item?id=37849310

[laurencerowe]

That doesn’t really have anything to do with this article which is about running JS quickly on server wasm runtimes.

[lll-o-lll]

Can you explain this a little more? This is for running JS server side right? So why would there be a DOM? Is the issue that JS libraries or other things you would be using assume a DOM?

[davexunit]

This type of comment shows up on seemingly every thread about wasm and it is so tiresome. Wasm can't do any I/O unless the host passes the module a capability to do so. If you pass a module some DOM functions then it can access the DOM.

[Waterluvian]

I’m curious though, does it gain meaningful access to the DOM in the case you described, or is it more just a proxy where it’s asking javascript, via some sort of channel, to manipulate the DOM?