How exciting. One of the great things about React is that it's just as much a pattern as a library, and with Rust macros and v-dom it should be rather easy to build something similar to JSX in Rust (with the proper Rust-isms of course). Can't wait for Rust to rule the web.
<i>>Virtual DOM libraries provide a declarative interface to the Web’s imperative DOM.</i><p>I'm not sure what this means. DOM is an object model for HTML. It is mutable, but HTML itself is definitely declarative.<p>Which brings up an interesting question. Why are DOM-diffs something that is done by userland libraries when it can and probably should be done by the browser itself?
Yes, I was thinking web developers, rather than using rust and wasm directly, would first get the benefits when the libraries they use start moving the heavy duty parts to it. Can't wait to see if someone uses this for building a react-like framework.
Firstly, congrats on shipping a virtual DOM lib in WASM. Hopefully, frameworks intent on using a V-DOM will greatly benefit from this.<p>Having said that, is a V-DOM required in 2019, if DOM updates are optimally batched, like in FastDom ( <a href="https://github.com/wilsonpage/fastdom" rel="nofollow">https://github.com/wilsonpage/fastdom</a> ). Decades of optimizing browser internals would surely account for not trashing the DOM, if updated optimally. So, is it required?
It seems memory fragmentation can occur, rather easily, if you hold onto a few of them.<p>> <i>The disadvantage of bump allocation is that there is no general way to deallocate individual objects and reclaim their memory regions while other objects are still in use.</i>