leptos VS Svelte

Leptos is a modern full-stack framework for Rust, built for fine-grained reactivity, server-side rendering (SSR), and seamless frontend/backend integration. It's similar in spirit to React with Next.js but offers Rust's safety and performance. Leptos integrates with Axum and provides a full-stack development experience — you can write your UI and backend in the same language and reuse logic between the two. It also supports hydration, island architecture, and async rendering. To get started with Leptos, install the CLI and scaffold a project:

How would you compare the two (Dioxus and Leptos)?

The link to Leptos is https://github.com/leptos-rs/leptos for those who need it.

Leptos

Rust? It's built clean from the ground up. The crates.io registry is full of modern, safe, composable libraries. You've got Axum, Rocket and Actix for backends, Leptos, Dioxus, and Yew for frontend, and more. Every library you use follows the same philosophy: safety, performance, and zero tolerance for ambiguity.

> To my knowledge there is not a Vue/React-WASM-type framework out there yet or any framework for building web apps in WASM (without starting from a blank canvas).

Not sure if these qualify, but these Rust web frameworks use wasm:

https://dioxuslabs.com/

https://leptos.dev/

https://yew.rs/

Or if you want more Next.JS like, but still fullstack framework there is https://leptos.dev/ and https://dioxuslabs.com/. Maybe dioxus being much more ambitious in its scope (not just web).

1: Actually, that's not true! I use Leptos in their "islands" mode for server side rendering. The entire page is sent as an HTML response, and there is little/no "hydration". The WASM file ONLY includes interactive "islands" that are explicitly marked with the #[island] attribute [0]. In other words, the server binary is handling most of the rendering, similar to if I used a templating tool like Askama or Tera.

2: Leptos is generally slower than vanilla JS, I believe for that reason, but comparable to major JS frameworks [1, 2].

[0]: https://book.leptos.dev/islands.html

[1]: https://krausest.github.io/js-framework-benchmark/current.ht...

[2]: https://leptos.dev/

Still doesn't look like it, this is the kind of interactivity I expect.

https://react.dev/learn/tutorial-tic-tac-toe

Where editing the code, immediately shows the GUI related changes on the neighbouring frame.

While what I see on https://leptos.dev/ is just screenshots, and there is nothing on that documentation you linked that provides the same interactive experience, one has to explicitly start a sandbox to host the whole machinery.

I primarily work on Windows, though I also use Linux, so I needed a cross-platform solution. I chose Electron for its flexibility and paired it with Svelte, TailwindCSS, and Vite-Electron. Vite made dev setup fast and clean, which I really appreciated.

a svelte5 spa

Svelte continues to earn a reputation as the joy-to-work-with framework due to its lightweight nature, elegant syntax, and compile-time reactivity. It is often used for side projects, hobby apps, and small websites, but Svelte isn’t just for passion projects.

tools: sveltekit, pocketbase, postmark, groq, docker, cloudflare, cloudflared.

The first time I visited https://svelte.dev , the non-flat-vector banner instantly won me. It just stands out from the world around it. I just sort of assumed the engineering was superior to the competition if they were going to lead with crimped metal (and was right).

Flat design has always struck me as an extremist response to an issue. Windows Vista required everyone to be on the same page design-language wise in order to look good, but can the same be said of Windows XP? You can make just a few parts of your app drop-shadowed, you can add some slight reflection gradients while keeping the whole thing matte, you do not need to get rid of all visual depth just to avoid the feeling of zeerust.

Svelte as the main framework. (Whimsy is my first Svelte project, actually! And Svelte didn't disappoint. Almost.)

We're going to build our Svelte application using the Svelte REPL sandbox (or just REPL) at svelte.dev. I recommend checking out all the great documentation at svelte.dev, like its Examples section showcasing Svelte's many features, as well as the cool interactive tutorial at learn.svelte.dev.

Svelte super clean frontend structure

In theory, “de-frameworking yourself” is cool, but in practice, it’ll just lead to you building what effectively is your own ad hoc less battle-tested, probably less secure, and likely less performant de facto framework.

I’m not convinced it’s worth it.

If you want something à la KISS[0][0], just use Svelte/SvelteKit[1][1].

Nowadays, the primary exception I see to my point here is if your goal is to better understand what’s going on under the hood of many libraries and frameworks.

[0]: https://en.wikipedia.org/wiki/KISS_principle

[1]: https://svelte.dev