sycamore VS leptos

Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.

Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.

Sycamore.

Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)

There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.

Sycamore is a reactive library for creating web apps in Rust and WebAssembly. https://github.com/sycamore-rs/sycamore

I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.

If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.

If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.

I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.

Why Krzysztof choose Tauri V2, leptos, and thaw-ui

I'm not here to present Leptos or Tauri, for that, just clik the links, ask Goole, or ClaudePilotGPTWhateverLLama... I'm not even here to make just a tutorial on how to get the two working -- if you see Tauri documentation on it is quite "terse," but still enough.

Lots of new frontend frameworks have been built on top of Rust, including Leptos, which happens to be one of the most popular ones. In this guide, we'll highlight why and how to migrate your JavaScript frontend to use the Leptos Rust frontend framework.

I don't know why OP felt moved to write this weird guide, https://leptos.dev is incredible!

https://github.com/leptos-rs/leptos/blob/main/flake.nix

You want a package? Add it to buildInputs.

You want to search a package: https://search.nixos.org/packages (or use the cli)

you want to test a package before adding it? nix-shell -p or nix shell for example.

Heck, even if you want it more easy, you could write a tool in less than 100 lines that adds packages names to .json/.yaml/.toml, which allows you to parse it using the nix language and a simple cli written with bash functions to add/remove packages if you wanted.

That's why it is hard for me to understand this project as a product, it seems like a wrapper to the most basic things :\

We use the fantastic Leptos framework for building the frontend. Besides that, we use the leptos-use utilities for connecting to the WebSocket server, serde for serialization, and rand for generating random numbers.

I'd use https://leptos.dev because you can use a fully typed language (Rust) that is super fast in the backend and also in the frontend (see https://krausest.github.io/js-framework-benchmark/2024/table...)

For the web-side, if you'd like to use Rust end-to-end we've had the best experience with Leptos: https://leptos.dev/