rust-rdom VS cope

There are two steps there: (1) rust-rdom working enough to be used by Yew, and (2) SSR support built out in Yew utilizing rust-rdom. Part (2) is pretty far away, but (1) is probably about halfway there. I think a more realistic use-case for the library is Sycamore which is much earlier and simpler than Yew. Sycamore support has a tracking issue here: https://github.com/rust-rdom/rust-rdom/issues/15

Hey, thanks for the suggestion. It already is largely generated - if you look at https://github.com/philip-peterson/rust-rdom/blob/a805f9439c380b3bf8b02572197a6b81eb425516/src/node/raw/mod.rs#L145 everything up to line 145 is basically defining the templates and then afterward is just instantiating that template for the different node types, with a few one-off customizations like for Document. The same is done in a few other places.

At one point I prototyped a wasm framework inspired by Solid[1]. The results were very promising—an implementation of js-framework-benchmark was 41KB (18KB gzipped), and perforrmance was close to vanillajs. The developer ergonomics were definitely lacking, though.

Benchmark results (look for _cope_)[2][3]

I definitely think whatever happens over the next few years, VDOMs are on their way out.

[1]: https://github.com/whatisaphone/cope/blob/master/crates/js-f...

I played around with a similar project last year (warning: hacky unmaintained project). I even went so far as to implement js-framework-benchmark with it. Spolier: it's pretty fast, in some cases on par with vanillajs, in others slower due to the WASM <--> JS interop overhead. I'm cautiously optimistic that once we have WASM reference types, WASM could be faster across the board.