I'm amazed at how far Leptos has come in such a short amount of time. What's more impressive is the excellent engineering and decision making by Greg and the team to get it there.
Watching this I came to conclusion that I prefer "non live coding" style of presentations. I find it much easier to follow when you show the code on the slide and invest more time into describing what it is and what it does, then watching all this typing and all possible errors one can stumble upon when writing code. As far for the Leptos project itself, fantastic work from everyone involved. 🙂
It isn’t usually as bad as this. He was poorly prepared and focused on the wrong things. If anything IMO he made Leptos look more messy than it actually is. Hope he learns from this. Greg on the other hand is a good communicator and advocate.
Leptos helped me build a website and API for an event last year and it was delightfully easy and fast (after a little help from Greg). I updated that site and API a month ago with the latest Leptos version and was again delighted with how all the changes made things easier with less boilerplate. Leptos's rate of development is amazing 🚀
I used leptos previously in a simple offline web app. I used leptos in a different way as template framework for a htmx web app. So it’s basically Axum backend only. Ich enjoyed this very much.
Great talk! Leptos is amazing, I hope it get's the attention it deserves. Together with Tauri it's the best thing since sliced bread for writing cross-platform apps.
State management in Leptos is realized through signals and derived values, while React uses hooks amd context. Combined with fine-grained reactivity (compared to React's heavy weight component-level approach), the performance and latency gains are incomparable. That also allows teams iterate much more frequent
I'm a Joe Java dev learning Rust at this moment. I think that if you cannot write this example from crash in a presentation, then it's not simple enough.
I'm amazed at how far Leptos has come in such a short amount of time. What's more impressive is the excellent engineering and decision making by Greg and the team to get it there.
Watching this I came to conclusion that I prefer "non live coding" style of presentations. I find it much easier to follow when you show the code on the slide and invest more time into describing what it is and what it does, then watching all this typing and all possible errors one can stumble upon when writing code.
As far for the Leptos project itself, fantastic work from everyone involved. 🙂
If we make a lot of typos when writing code, I guess that the IDE is not good enough.
@@avalagum7957 This has absolutely nothing to do with the editor
It isn’t usually as bad as this. He was poorly prepared and focused on the wrong things. If anything IMO he made Leptos look more messy than it actually is. Hope he learns from this. Greg on the other hand is a good communicator and advocate.
Leptos helped me build a website and API for an event last year and it was delightfully easy and fast (after a little help from Greg).
I updated that site and API a month ago with the latest Leptos version and was again delighted with how all the changes made things easier with less boilerplate.
Leptos's rate of development is amazing 🚀
Amazing job Leptos team!
I used leptos previously in a simple offline web app. I used leptos in a different way as template framework for a htmx web app. So it’s basically Axum backend only. Ich enjoyed this very much.
now i know you're germany
YOU MADE MY DAY, I WAS STUCK WITH LEPTOS AND YOU HELPED ME GET IT WORKING,... thanks for the sharing of your knowledge ☕
Great talk! Leptos is amazing, I hope it get's the attention it deserves.
Together with Tauri it's the best thing since sliced bread for writing cross-platform apps.
Incredible, great presentation! 🎉
Looks cool, but still have one question. Why?
I am not sure about use case for Leptos. It looks like React in Rust.
What are the use-cases for React?
It is not React at all. It's Leptos Signal
State management in Leptos is realized through signals and derived values, while React uses hooks amd context. Combined with fine-grained reactivity (compared to React's heavy weight component-level approach), the performance and latency gains are incomparable. That also allows teams iterate much more frequent
Wow you look dumb 😂 non dev spotted!
I'm a Joe Java dev learning Rust at this moment. I think that if you cannot write this example from crash in a presentation, then it's not simple enough.
Люди, которым нравится писать ТАКОЕ на раст - не от мира сего. Им нравится натягивать сову на глобус при помощи микроскопа. Зачем?
Leptospirosis? really?