267

Lemmy core devs have started work on a new front end using leptos (lemmy.ml)

submitted 1 year ago by snaggen@programming.dev to c/rust@programming.dev

79 comments fedilink hide all child comments

Quoting the author

I’ve starting working on a lemmy front end called lemmy-ui-leptos using leptos, a Rust UI framework with isomorphic support, and tailwind + daisyUI for the component styling. This could eventually replace the frankenstein’s monster that lemmy-ui has become.

top 50 comments

sorted by: hot top controversial new old

[-] Brochetudo@feddit.de 18 points 1 year ago

Isomorphic support? Isomorphic to what?

[-] jimmy90@lemmy.world 23 points 1 year ago* (last edited 1 year ago)

Same code renders ui and handles interactions on both server and browser/app

See the leptos docs on SSR

[-] JakeHimself@programming.dev 1 points 1 year ago

Itself, via the identity function

[-] FarLine99@lemm.ee 15 points 1 year ago

Very good news!

[-] popcar2@programming.dev 14 points 1 year ago

Sounds good, but I hope it doesn't take too much time that they ignore some of Lemmy's issues and missing features.

[-] nerdblood@programming.dev 3 points 1 year ago

This is cool. I'm a front-end focused dev by trade and have been 11 years now. I've been picking up Rust as a side hobbie for 6 months or so and have not even peaked at these front-end frameworks. I know Lemmy is all about Rust, but I still think it's pretty cheeky they're using Rust for the front-end.

About Leptos specifically... If there's no shadow dom / rerenders and not trying to be react, I already like it better than it's competitor.

[-] argv_minus_one@beehaw.org 2 points 1 year ago* (last edited 1 year ago)

Isomorphic rendering seems horribly inelegant.

My first instinct is to just use server-side rendering for this, although that may not be possible since posting a comment involves rendering part of the page on the client side.

In light of that, my second instinct is to render entirely on the client side, but then Lemmy won't work without JS, which may or may not be a problem. Mastodon seems to get away with it, but I dunno if Lemmy can. Also, client-side rendering makes it difficult to avoid breaking the back button, which the UI currently does.

Sheesh. Web development is such a mess.