Hacker News new | past | comments | ask | show | jobs | submit login

WebAssembly has no good story for the DOM.



We have canvas and WebGL.

And just because it isn't there today, it doesn't mean it won't be there tomorrow.


i feel like that's on purpose...we can engineer all these crazy things, but getting good DOM access? naw not possible


wasm is an MVP, they fully intend to add DOM support: http://webassembly.org/docs/future-features

Its just that implementing the DOM requires a lot of other (complex) things 1. Stable JS object ABI 2. Integration with the GC garbage collector 3. Better integration with modules

Personally, I'm hoping that we actually get a lower-level subset of the DOM apis that doesn't rely on as many OO features so we can bind to it easier, and avoid more DOM manipulation overhead (though I have no idea what this would look like).


Personally I'd like to see an experimental mode in Quantum/Servo with an RPC interface to render directly to the display list, possibly with an intermediary like a vector of VDOM operations.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: