Thanks Chris and Greg! Great video summary, and great library. This is my favorite frontend library so far in rust, primarily for syntax/feel of the code.
thanks so much for the video ! just getting into rust - mostly bc of stumbling across “no boilerplate” on here i’m a long-time fan of functional, reactive programming, haskell, lisp, etc,, and less-so of oop.. but id always heard abt rust at a distance ! and i basically just thought it was a new c lmao the way rust combines the absolute most metaprogramming possibilities w a lovely type system, and in that structs and enums w no “null” and the elegant ownership system enabling a gc-less experience.. wew i’m super sold and now videos like this r helping me figure out what crates from the massive supply,, have thinking and systems in line w how i wanna code projects using rust as i start to learn it tysm
This looks promising. Thanks for the coverage. I think egui and Bevy (rendering only on events or during animations), or at least other web renderers that don't use the DOM (they use a ) except for metadata and SEO, do deserve some attention, but there will always be the need for complete DOM integration with both HTML and Rust idioms. SSR is currently a bonus, but I think that with code splitting it will become less needed over time. I'm not sure why SSR/hydration has become so popular because, even with a very large site, code splitting already solves the problem of quick loading.
Just want to say that I appreciate these videos that you do evaluating different frameworks. I am looking around for a nice framework to kind of "settle on" to build a project of mine, but I am honestly having a hard time to decide. Leptos do look promising, I like a lot of what they are doing, it seems simple yet powerful. But it is new and in active development and things can change rapidly. I was wondering, when you have been looking around, what is your feel for the future of some of these newer frameworks, like Leptos? Do you think they will evolve into something that could actually be viable for production use in the future, or are there any hints or signs of them possibly dying before reaching their potential?
So just replying as the author of Leptos - to me, 0.0.x is trying to communicate "use at your own risk, there may be bugs" and not so much "APIs will change wildly and break your app." The core fine-grained reactive programming model in particular is not a big innovation but something pretty well established in prior art, so I wouldn't expect many breaking changes there going forward. Of course there's always a risk in libraries that are basically single-maintainer. You know that something like Yew certainly isn't going to disappear. But I don't plan on dropping Leptos or anything.
@@gbjxc Thank you for your reply! I understand what you are trying to communicate here. And I appreciate the fact that you do. It's also nice to hear your personal thoughts on this as it is your own project. I have to say that, as little as I know currently, I am feeling excited about Leptos. It feels more "natural" if you can call it that or more familiar, and much less boilerplaty than other similar frameworks. I am excited to try it out for myself. And thank you for putting your framework out there. Keep up the great work!
This is my first time seeing Leptos. It looks very interesting. Feels a lot like sycamore. Thank you. For some reason, I'm more comfortable with the elm-like view macros in sycamore. It's a bit easier for me to read. But I like the JSX too.
In my experience, it's faster at runtime, and has nicer ergonomics (copies instead of clones everywhere), and it's JSX is more featurefull (works well with custom elements and overloaded attributes). It has less support for things like larger scale state management (yewdux) however.
Thanks, Chris - great video! I've really appreciated the thoughtful comparisons between/across frameworks. (I'm the Leptos maintainer)
Thanks Chris and Greg! Great video summary, and great library. This is my favorite frontend library so far in rust, primarily for syntax/feel of the code.
This is the framework that most interests me between it, Yew, and Sycamore. Thanks for covering it!
thanks so much for the video !
just getting into rust - mostly bc of stumbling across “no boilerplate” on here
i’m a long-time fan of functional, reactive programming, haskell, lisp, etc,,
and less-so of oop..
but id always heard abt rust at a distance ! and i basically just thought it was a new c lmao
the way rust combines the absolute most metaprogramming possibilities
w a lovely type system, and in that structs and enums
w no “null”
and the elegant ownership system
enabling a gc-less experience..
wew i’m super sold
and now videos like this r helping me figure out what crates from the massive supply,,
have thinking and systems in line w how i wanna code projects using rust as i start to learn it
tysm
Fantastic rundown Chris. You found one that I didn't know about (of course). Keep em coming, my friend!
This looks promising. Thanks for the coverage. I think egui and Bevy (rendering only on events or during animations), or at least other web renderers that don't use the DOM (they use a ) except for metadata and SEO, do deserve some attention, but there will always be the need for complete DOM integration with both HTML and Rust idioms. SSR is currently a bonus, but I think that with code splitting it will become less needed over time. I'm not sure why SSR/hydration has become so popular because, even with a very large site, code splitting already solves the problem of quick loading.
Great video, very helpful in navigating all the different rust frameworks. Thanks
Just want to say that I appreciate these videos that you do evaluating different frameworks. I am looking around for a nice framework to kind of "settle on" to build a project of mine, but I am honestly having a hard time to decide. Leptos do look promising, I like a lot of what they are doing, it seems simple yet powerful. But it is new and in active development and things can change rapidly.
I was wondering, when you have been looking around, what is your feel for the future of some of these newer frameworks, like Leptos? Do you think they will evolve into something that could actually be viable for production use in the future, or are there any hints or signs of them possibly dying before reaching their potential?
So just replying as the author of Leptos - to me, 0.0.x is trying to communicate "use at your own risk, there may be bugs" and not so much "APIs will change wildly and break your app." The core fine-grained reactive programming model in particular is not a big innovation but something pretty well established in prior art, so I wouldn't expect many breaking changes there going forward.
Of course there's always a risk in libraries that are basically single-maintainer. You know that something like Yew certainly isn't going to disappear. But I don't plan on dropping Leptos or anything.
@@gbjxc Thank you for your reply! I understand what you are trying to communicate here. And I appreciate the fact that you do. It's also nice to hear your personal thoughts on this as it is your own project.
I have to say that, as little as I know currently, I am feeling excited about Leptos. It feels more "natural" if you can call it that or more familiar, and much less boilerplaty than other similar frameworks. I am excited to try it out for myself.
And thank you for putting your framework out there. Keep up the great work!
@@JesperHasselquist
I'm in the same boat, going with dioxus!
9:00 that’s so fkn cool !
no vdom just reactivity ~
This is my first time seeing Leptos.
It looks very interesting. Feels a lot like sycamore. Thank you.
For some reason, I'm more comfortable with the elm-like view macros in sycamore. It's a bit easier for me to read.
But I like the JSX too.
Now that you're covering web framework crates it would be awesome to also cover egui.
wow leptos has really nice dx from what i’ve seen in this video
yoooo wait it has streaming and ssr 👀
has ryan seen this :0
hahaha the hackernews example
You should make a video on blockchain programming in Rust
I don't work with blockchain tech in general
is it better than yew.
In my experience, it's faster at runtime, and has nicer ergonomics (copies instead of clones everywhere), and it's JSX is more featurefull (works well with custom elements and overloaded attributes). It has less support for things like larger scale state management (yewdux) however.
It definitely looks more solid.
thank you!
If you're building a UI library or framework and not using a flavor of JSX, you're doing it way, way, wrong.