asm-dom VS wasmr

Aside from Blazor there's already some other projects like Yew (rust), seed (rust), asm-dom (C++) and vugu (Go) and more that have decent followings and activity. A lot more (especially managed languages) are waiting for some features to come online like wasm GC and host bindings (direct wasm access to browser apis which includes the DOM). It'll take a bit of time, but it'll get there eventually.

FWIW if you look around, C++ and Rust libraries for DOM manipulation exist (I haven't searched for other languages which compile to WASM):

https://github.com/mbasso/asm-dom

https://github.com/sycamore-rs/sycamore

I think solving the problem of DOM access on the library level is exactly the right way to tackle this problem. The library user don't need to care about specific WASM features, and the library implementation can be simplified when those WASM features become available (and also implement per-browser fallback paths)

Wasm is already around for a while. There are probably some libs to access the dom and frameworks around that wrap the js part completely Found this after a short search https://github.com/mbasso/asm-dom Also Blazor seems to work fine, but didn't really test it beside playing around a little bit with it

Thanks for the kind words! :-) Yeah, you've got a good description of the use case for it. You give me too much credit though. :-) It's built on top of Emscripten, which handles a lot of the low-level bindings between C++ and the browser. Also, asm-dom helps fill in a big gap between C++ and the DOM.

Not to add more confusion but to promote a cool project, there is wasmr which allows to run WebAssembly inside R, just like Wasmer Python embedding allows to run WebAssembly inside Python. Just wanted to mention this project because we are talking about R :-).