What Leptos Does
- Fine-grained reactivity — signals (like SolidJS, not VDOM)
- SSR — server-side rendering with streaming
- Hydration — pick up server-rendered HTML on client
- Server functions —
#[server]functions called from client - Routing — file-based or declarative
- Suspense — async data loading boundaries
- Islands — partial hydration for minimal WASM
- Actix or Axum — server integration
Comparison
| Framework | Reactivity | SSR | WASM |
|---|---|---|---|
| Leptos | Signals | Streaming | Yes |
| Dioxus | Signals | Yes | Yes |
| Yew | VDOM | Yes | Yes |
| SolidJS | Signals | Yes | No (JS) |
FAQ
Q: Why choose signals over VDOM? A: Signals only update the DOM nodes that change (O(1)); VDOM needs to diff the entire tree (O(n)). Better performance and a smaller WASM bundle.
Q: Similar to SolidJS? A: Very similar. Leptos' API design is heavily inspired by SolidJS, but it's full-stack Rust (type safety + WASM performance).
Sources
- Docs: https://leptos.dev
- GitHub: https://github.com/leptos-rs/leptos
- License: MIT