Leptos 0.5: No More Scope!

[@sadramohh]

Let's go Leptos! Really excited to see this wonderful framework evolve.

[@gbjxc]

We aim to please! (Not the royal we - there were I think 40 contributors to this release? And I had to be convinced into some of the nicer DX wins 😂)

[@macaco_agiota]

Wow.. it's amazing

[@codiumyt]

What do you think about Catppuccin Mocha? I believe it looks nicer than NightOwl.

[@chrisbiscardi]

I haven't heard of it, will put it on my list to check out

[@ThrashmIO]

Having "migration comments" for crates would be great. You could do "@deprecated:use("get"):move_paramter(0,1):parameter(0, "blah")" and you could easily GUI or CLI change based on something like that.

[@chrisbiscardi]

This is pretty common in the JS ecosystem under the name "codemods". I haven't seen as much structured update tooling in the Rust ecosystem. There's cargo fix and cargo clippy --fix, but these are fairly new and don't accept userland fixes afaik. So something like Leptos's .read -> .get update or the scope removal wouldn't be accepted, but more globally applicable fixes could be merged into upstream. Yew's 0.21 update included some suggested find/replace commands: yew.rs/docs/migration-guides/yew/from-0_20_0-to-0_21_0

[@Tanja42]

Love the developments in the ecosystem 🎉

[@mustafazakiassagaf1757]

I'm so hyped with leptos island. I love using astro and can't wait to write those paradigm in leptos

[@gakman]

Thanks for the overview. Time to update my site!

[@TomasSandven]

I’ve been wanting to get into Leptos for a while now, but I’m a little worried about the developer experience. How would you rate the developer experience compared to something like Svelte or Next.js? Have you had any issues with the HTML-like macro syntax, for example? What about hot reloading?

[@chrisbiscardi]

The hot-reloading speed compared to a very direct client-only low-js environment will be a bit slower, but is comparable to any larger js framework. You can expect to wait for 1s or so on changes when working with the cargo-leptos tool, which would imply that you're also building the server and the client. In practice I don't find this to be an issue. The HTML-like macro syntax works well, with the main drawback being the lack of built-in autoformatting. There is a tool (leptosfmt) that can auto-format for you, and its relatively easy to set up to run on-save in vscode, but its not built-in. I would frame Leptos as being a little more rough around the edges than the experience JS-focused devs have come to enjoy but good enough for daily usage. I don't find myself getting frustrated by it being "slow" or similar. That said, I very much enjoy the process of writing Leptos code. Being able to use Rust's type system, and rust-analyzer especially, makes things like refactoring much, much more pleasant. I don't have to wonder if I "got everything" in a refactor. Upgrading from 0.4 to 0.5 for example, involved me relying a lot on the compiler to tell me what I needed to change, changing that, and then being done. I wouldn't let a fear of the developer experience stop you from trying it out.

[@dnels493]

@@chrisbiscardi for me with these changes in 0.5 are putting me over the edge to go ahead and use leptos. I want to get out of JS land and just be full time in rust.

[@jaabberwocky5484]

@@chrisbiscardi Thanks for the detailed write-up. I've been deep in the React ecosystem for the past couple of years, and more recently in the last year, in Svelte. Given how much I like using Rust for generally everything else, you just convinced me to give Leptos a try!

[@alighahremani4626]

Wonderful 👌 Can you do a video about Leptos vs Dioxus vs Yew by any chance?

[@chrisbiscardi]

I have a number of videos on the technologies separately (here's a playlist link). What are you looking for in a three-way comparison video? kzbin.info/aero/PLWtPciJ1UMuBpRg1KbXqxE5WOdY9ze37S

[@indierusty]

Please make some videos on Bevy ECS implementation in depth like how Any type works for beginners rust user.

[@chrisbiscardi]

I've put something on my list for this. I have a few other videos to get through first though so don't know when it'll get made.

[@indierusty]

@@chrisbiscardi bevy_esc_video().await 😊

[@ThrashAbaddon]

Thanks. :)

[@jrmoulton]

Nice! Great overview

[@chris3079]

how long before they hit 1.0 does anyone think?

[@chrisbiscardi]

My guess is probably a while. 1.0 in the Rust ecosystem tends to hold more meaning than 1.0 in the JavaScript ecosystem, and Leptos is still iterating on APIs, like islands and the new reactivity/scope changes.

[@chris3079]

It has same meaning in js/ts. Not sure why you think rust would be different I use qwik for my front ends. Love it. But I started it using before “1” release and wish I had just waited till, the api changes were frustrating.

[@chrisbiscardi]

​@@chris3079 yeah definitely if API changes like the ones listed in this video are frustrating for you, I would wait. For context on my initial semver comments if you're interested: My impression of the difference is crates like serde having hit 1.0 in 2017 and maintained compatibility in a 1.0 state since then, which isn't something I experienced in the JS ecosystem as much.

[@chris3079]

@@chrisbiscardi very good point, i take back my statement regarding 1.0. fwiw, the API changes here don't bug me. But qwikjs and deno i had pains with getting to 1.0. would love if you did more embedded stuff, its fun haha