top | item 41368657

Compilation of JavaScript to WASM, Part 2: Ahead-of-Time vs. JIT

93 points| cfallin | 1 year ago |cfallin.org

8 comments

order

_m1x6|1 year ago

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|1 year ago

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

lll-o-lll|1 year ago

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|1 year ago

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.