I'm currently reading up on Leptos and what looks like its major contender, Dioxus [1] in planning for next project. (acknowledging here that Yew [2] is maybe the OG Rust full stack / frontend framework, but I'm not considering it at this time)
Note that Leptos is interesting because it _does not use a virtual DOM_, unlike Yew and Dioxus which are React-like.
We already write our backend in Rust; why not use it for the whole stack and stop worrying about e.g. the Typescript object falling out of sync with the API struct?
I think that the idea (before they add the memoization that the docs mention) is that this only serves as a way to name a computation, so you don't have to litter the same logic in multiple places but can instead just call the lambda instead
Edit to add:
> Why use React style capitalized names for components, like App instead of app? It's a bummer when framework breaks a languages style conventions.
I understand the remark, but on the other hand I also don't mind it; even like what they've done. I think it's useful as a signal that this this is component code, and has the added benefit that it looks familiar to other frontend code
A derived signal is generally a closure. The word just reminds you that the signals have scope-based tracking so the framework knows when they have become invalid and need to run again
> Using a component in the view looks a lot like using an HTML element. You’ll notice that you can easily tell the difference between an element and a component because components always have PascalCase names.
14 comments
[ 2.7 ms ] story [ 42.9 ms ] threadHere's a nice comparison of the Rust frontend frameworks: https://github.com/flosse/rust-web-framework-comparison#fron...
Note that Leptos is interesting because it _does not use a virtual DOM_, unlike Yew and Dioxus which are React-like.
We already write our backend in Rust; why not use it for the whole stack and stop worrying about e.g. the Typescript object falling out of sync with the API struct?
[1] https://github.com/DioxusLabs/dioxus/ [2] https://yew.rs/
Why use React style capitalized names for components, like App instead of app? It's a bummer when framework breaks a languages style conventions.
I'm confused by 'derived signals'. How is a derived signal different than a signal?
> Using a derived signal like this means that the calculation runs once per signal change per place we access double_count
https://leptos-rs.github.io/leptos/view/02_dynamic_attribute...
Edit to add:
> Why use React style capitalized names for components, like App instead of app? It's a bummer when framework breaks a languages style conventions.
I understand the remark, but on the other hand I also don't mind it; even like what they've done. I think it's useful as a signal that this this is component code, and has the added benefit that it looks familiar to other frontend code
that is what a rust closure assigned to a variable does right. Why does a derived signal need a new name?
> Using a component in the view looks a lot like using an HTML element. You’ll notice that you can easily tell the difference between an element and a component because components always have PascalCase names.