WASM UI with Signals - Leptos's first release

[@marcusrehn6915]

Rust community is remaking React, Svelte and Solid in Yew, Sycamore and Leptos. And I am here for it ❤

[@ryanleemartin7758]

Sycamore is Svelte like? I didn't know that. I might have to check it out.

[@prevv3366]

Svelte = Sycamore???

[@prevv3366]

that would be cool

[@sadramohh]

Rewrite it in rust!

[@wadecodez]

hope someone makes an equivalent to vue

[@nathanielbutton9878]

Let’s gooo! I’ve been watching Leptos closely in the last few months and am so excited for 0.1. Very happy to see you covering the new release

[@aqua3418]

In the future, the context (Scope) may no longer be needed to pass into things like `view!`. That'll be nice. There's a rework currently going on with this

[@cocoiyeah]

I've been waiting for the next wave in Development scene and Leptos deliver it!

[@michaelscofield1970]

As much as I would love a pure Rust webdev environment, this isn't it sadly. Svelte and SvelteKit will still be my go-to.

[@chris.dillon]

Yeah. Webtech for web (currently). I understand the impulse for rid the world of JS but backends are unlikely to unify under one language. Something like Tauri is great because it's strength on strength. Rust for a CLI/daemon, any webtech stack for UI.

[@climatechangedoesntbargain9140]

Why?

[@jaysistar2711]

I'm going to use this to see what's missing. If nothing's missing for my needs, I'm switching to it.

[@everythinggoes850]

Me too.

[@RG-em1gg]

I've been playing around with serveral rust web frontend frameworks recently and this looks quite interesting as well. I just cant get leptos to run on my machine (windows). There are always problems with compiling openssl stuff even though I was following some advice from others to fix it (vcpkg etc.). Maybe anyone has an idea here how to solve the issues with openssl on a win10 machine?! :)

[@akillersquirrel5880]

Honestly, running within WSL would be the easiest way to get things working

[@climatechangedoesntbargain9140]

Be more specific with your issues

[@chrisbiscardi]

if you're running the leptos examples, then you might want to make sure you're using rustls instead of openssl specifically when it comes to the reqwest dependency, which relies on ring under the hood. You'll have to disable the default features and then enable the rusttls-tls feature: docs.rs/reqwest/latest/reqwest/

[@RG-em1gg]

@@akillersquirrel5880 I was setting up my windows with wsl and now there are no problems. Thanks for that hint 👍

[@Zynh0722]

What are you using for window management?

[@chrisbiscardi]

Yabai

[@lMINERl]

I need someone to tell me why i see alot of vids about leptos than sycamore both same thing both use signals only difference is some one adopts object like syntax other one jsx like syntax. If feel sycamore is way mature than leptos . If someone knows plz reply to this im a bit confused or there is some git drama im not aware of.

[@rez188]

Leptos' popularity isn't really about syntax, it's about speed. Leptos is the fastest web framework. I don't just mean rust, it's faster than any js framework as well. Even svelte is slower

[@ReedoTV]

It's that meme where the guy is looking over his shoulder at Leptos while Sycamore stands next to him looking annoyed

[@lMINERl]

@@rez188sycamore and leptos both of them use rust, both of them wasm . well about speed i dont think some milliseconds will make that a huge deal i think both has same speed.

[@chrisbiscardi]

fwiw, on this channel I have also covered and intend to continue covering sycamore/perseus (and yew, etc). I don't know of any drama between any of the projects. IMO, especially this early in the Rust/Wasm/UI story, it would be unhelpful at best to say one is better than the other. I've seen "project vs project" (often VC funded "project vs project") happen in other ecosystems and its always a whole mess so I hope that doesn't happen here and that people understand they're both going to evolve a lot before 1.0 is released in either project, and so is the state of Wasm in the browser. For my personal work, I do a lot of exploration. Both for videos and also just for general knowledge so I can keep tabs on what's going on. So I chose Leptos for a recent project because I thought it would be fun to work with. I will also do more work with sycamore and yew though, and would be more likely to suggest sycamore or yew to a client because of the maturity of those projects.

[@bigmistqke]

@@rez188 just checked the js framework benchmark and according to those results, leptos 0.1.0 appears to to be slower then sycamore and just behind Vue. So it's far from the fastest.

[@SatyajitGhana7]

is that yabai?

[@chrisbiscardi]

Yes

[@driedurchin]

Is it just more or is the green text output by leptos a slightly different shade of green than the cargo green?

[@chrisbiscardi]

It does seem different to me too. I'm not sure if it is intended to be the same or not.

[@sawood2010]

I'm learning rust now and I feel like it and WASM are the future of a lot of apps; web dev for sure. Is it reasonable to move the html to a separate file though? I come from Angular and I can't stand having the logic and html in the same file. I actually prefer the separation of concerns between files, otherwise I get lost in all the lines. I have to compartmentalize everything. also, on the server side of things... do you prefer diesel or sea orm, or something else? I have currently have an actix api working with diesel, but sea orm has async support. I personally don't like to use raw sql more than I have to. I am too spoiled to type help and auto-complete!

[@RootsterAnon]

my man, my man, my man... have you ever heard of Collapse/Expand functionality in IDE's? Also, don't you ever mention Angular again, you swine.

[@chrisbiscardi]

> Is it reasonable to move the html to a separate file though? It would be reasonable, but it is not supported by any of the Rust/Wasm frameworks that I know of at the moment. macros are fully capable of reading in external files so you could imagine a `view_from_template!` macro that reads in an external file. I don't know how that would affect the experience of using the framework though. > do you prefer diesel or sea orm, or something else? I tend to stay away from ORMs for my own work. I use sqlx which lets me write SQL in separate files and check them against the database at compile time.

[@sawood2010]

@@chrisbiscardi appreciate it. I've decided to start using actix for all my api needs. I still need a good replacement for Angular. It has become too bloated and dependency hellish. I'm currently toying with sveltekit and love it, but I really want to get away from node. I'm trying to find a good rust/WASM option for the FE. any recommendations for anything that's production ready or semi-close?

[@chrisbiscardi]

@@sawood2010 I'd look to Yew or Perseus (built on Sycamore) if I was looking for something in the Rust/Wasm space that was more mature than Leptos.

[@arkapoddar3727]

Congratualtions

[@__noob__coder__]

Why not work on yew instead. Looks similar to yew. I hope next they dont start coming out with 1 rust frontend framework everymonth like javascript.

[@chrisbiscardi]

yew and leptos take different enough architectural approaches to the problem that trying to make one into the other wouldn't work very well. I would also suggest that people making new frameworks isn't ever really a problem and even if it was, Rust is far from having "too many".

[@maninalift]

The existence of Percy is a cause of adoption anxiety. Why is there another framework that seems so similar? The only difference seems to be that it is less mature and perhaps more modular

[@chrisbiscardi]

Wasm is still an early field, especially for UIs written in non-javascript languages. So I expect to see more frameworks pop up as people get a feel for what's possible and what the constraints are, even if they're very similar. Due to how new it is, for example, it's a harder sell to bet on Leptos right now than say, Yew or Perseus which are a bit more established and stable. At some point you have to either write some test applications to inform yourself more about the tradeoffs or commit to *something* for a project even though it might not be the perfect choice. Personally I expect the wasm/rust/ui landscape to change a lot over the next 3-5 years, so I'm only making fairly short term choices with that in mind anyway.

[@marccawood]

Can’t help feeling wasm is the next applet/flash/silverlight. Just wait for the first CVE and all the browser vendors abandon it.

[@chrisbiscardi]

applets had security issues, definitely, but neither flash nor silverlight died out because of security issues. IMO the advent of the iPhone, html5, and iOS not supporting the flash are why they aren't around anymore and wasm doesn't rely on the NPAPI tech that applets/flash used. Wasm by contrast has spec and browser support, not vendor. whether or not wasm becomes "the next javascript" is the big question, IMO, which we won't see pan out for a few more years.