@luizgrocco

Every time I listen to a Greg talk / watch a Greg Video I feel like I've understood 100% of what he is saying. Such a great talker and truly knowledgeable about the topics he's talking about.

@christopher8641

Greg is a genuinely positive person to discuss code with, he is always around the leptos discord helping people out and hotfixing obscure issues. Great talk!

@flwi

Man - he is such a great speaker! That hour went by in no-time.

@JR-wu3rx

Loved this talk. The refresher on web framework history and its different stages was clear and easy to grasp. I think code splitting will grant developers much more control over when data gets streamed to the client. I hope one day to get my own PR merged into Leptos. Thanks Greg and Ben for still being so consistent and reliable after several years into this community project.

@Owerewower

Greg usually mentions the benefits of compressing wasm as well. You can also go through the effort of instructing cargo to compile the standard library, in order to "shake loose" the parts that are not needed for your application.

@Jack-lb5ih

Greg is an absolute hero.Huge amount of respect for all the work he's put into leptos. Incredible project with a very bright future.

@abhi3700orig

I’ve been building my production app in Rust due to its backend and blockchain-related dependencies. I must say, Rust-based web apps are incredibly fast, aside from the initial overhead of downloading the WASM. One effective way to mitigate this is by using multiple layouts within a single route, reducing the need to download WASM separately for multiple routes.

I am using dioxus where RSX is pretty cool. Also, I get to use the readily available tailwind-css templates inside my web app for beautiful material-design UI/UX.

One caveat though:
As these rust frameworks are pretty new, so in many places in order to use web API like for copying to clipboard, share,.. you have to rely on low-level libs:
- wasm-bindgen
- wasm-bindgen-futures
- web_sys
- js_sys

@JacobyB

Nice video and i like the part showing lazy-loading.

@notathingsaying

Thank you so much for this engaging and well spoken talk!

@tacticalassaultanteater9678

I've got to try these again, with Yew a few years ago I felt like I had to fight against the language's nature every step of the way, but this is all very compelling!

@DavidAlsh

Love the talk! The most important missing feature in wasm for me is multi-threading!!! I want fearless concurrency on the web. Not needing to ship JavaScript glue code would also be nice, looking forward to the day I can include a .wasm file in a <script> tag.

@Galakyllz

That was a great talk, Greg. Thanks!

@mariinkys

Awesome talk, always a joy to listen to Greg!

@ahmadolukotun3884

When he said to fill in the gap and placed 5:44  R. First thing to come to mind was Ruby

@AlexDubois

Good talk however an important topic has not been addressed: CDN/caching. Is it possible, or is there work in progress to sign-verify signature and lazy load modules?

@TonyAlvesDev

GOAT. There's not much else to say!

@Wooby1Dooby1

It's a very well-thought-out framework I must say. Anytime I think 'how tf am I going to do this?', there's a page in the docs dedicated to exactly that!

@celophi

We've been writing our web application using Blazor WASM for the past 3 years.

@Mike-zx7lq

Really surprised to not see any mention of htmx during this talk. It's a fantastic option to enable frontend interactivity for any normally backend-only language, including Rust! Not a good fit if you need massive interactivity (you're building the next Figma), but for the vast majority of cases I've been loving it. The model is very simple to understand, and lets you keep all your behavior in one place using Server-Side Rendering, but with a good user experience. There are plenty of calls to the backend, yes, but from any JS framework they're mostly calls I would be making anyway via a JSON data API -- unless I've built a really thick client that handles a bunch of state client-side. With htmx I'm just returning slices of HTML from the server instead of JSON objects that get interpreted by a thick client.

@codeitlikemiley

i have been waiting for code splitting now its been added so as the island architecture… we are in the right position to be using rust and leptos as soon as more and more people adopts rust