sycamore

I looked briefly, but is anyone aware of the differences between Yew[1] and Sycamore[2]? Presumably they are both Elm-influenced(?) Rust web UI libraries named after trees, but it's unclear to me why I should use one versus the other. 1. https://github.com/yewstack/yew 2. https://github.com/sycamore-rs/sycamore

The website itself is made with Sycamore! There are also a bunch of examples at https://github.com/sycamore-rs/sycamore/tree/main/examples You can see the deployed versions at https://examples.sycamore.dev/<example name>/ for instance: https://examples.sycamore.dev/todomvc/

For this there's Leptos and a half dozen other "DOM in Rust" frontend frameworks: https://github.com/leptos-rs/leptos These are already orders of magnitude faster than React, and as the WASM<->DOM bridge improves, they will only get faster. Sycamore: https://github.com/sycamore-rs/sycamore https://sycamore-rs.netlify.app/examples/todomvc/# Dioxus: https://dioxuslabs.com/ In about 3-5 years these frameworks will start to consolidate and reach maturity. It's already possible to build reactive isomorphic apps in Rust. If you haven't checked out Actix/Axum, it feels a lot like Python/Flask. The ecosystem is coming along quickly.

While React's declarative style and composability are great, and its ecosystem reigns supreme, I really dislike all the tiny issues that one has to learn to deal with(referential equality for hook dependencies, the side-effects of batching setState calls, figuring out when a specific useEffect call is called, the fact that useMemo and useCallback don't provide semantic guarantees that one can rely on to avoid rerenders, ...etc). I've been meaning to try out some "truly reactive", vDOM-less libraries like Svelte, SolidJS, and Sycamore-rs [1] for a while now. Today, I ran into a library that ports all of SolidJS's API to React, so that one can still use React, but in a truly reactive way, and it's written by the author of SolidJS himself! I haven't tried it out but I was so excited that I had to share :) The advantage that I'm hoping this

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)

What are your thoughts on Sycamore? It uses Svelte-style compile-time reactivity. https://github.com/sycamore-rs/sycamore

Sycamore looks interesting, though it needs some more ergonomic improvements before it becomes more widely usable. https://github.com/sycamore-rs/sycamore

Not affiliated, but an alternative to Seed or Yew is a new lib: https://github.com/sycamore-rs/sycamore AFAIK Seed and Yew target the VDOM stuff which has always been an unnecessary overhead, Sycamore does what Svelte does. It's very early days for Rust/WASM/Frontend, but all of this progress is very promising.

There are some VDom-less libraries popping up now. https://github.com/sycamore-rs/sycamore