asm-dom VS snabbdom

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.

I like to use snabbdom to demonstrate concepts in several of my posts because it is short, simple, powerful and uses several techniques that are relative to the topics I wrote about in the past. Snabbdom is a front end JavaScript library that lets you work with a virtual DOM to create robust web applications. They focus on simplicity, modularity and performance.

A good repository to learn from this concept is snabbdom, a virtual DOM library that focuses on simplicity, modularity, and powerful features to improve performance when working with the DOM.

Compared with other virtual DOMs (see snabbdom, virtual-dom), it's significantly faster. These older methods use node-by-node diffing, or the traversal and comparison of the node tree in order to calculate the optimal DOM modifications to reduce reflow and repaints.

I was disappointed by commitlint and commitizen, so I wrote this tool. IMO having such a tool makes you think more about your commit messages and thus makes you write better ones. See these for example: https://github.com/snabbdom/snabbdom/pull/948/commits