leptos VS dioxus

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.

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.

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/

> The web had this before briefly. Back in the 90s and 00s, some people just wanted to use Flash.

WebAssembly is different. WebAssembly brings every language to the web. Flash didn't.

WebAssembly can render to canvas and enable applications that compile to desktop, mobile, and the web. UI libraries like Avalonia do this: https://avaloniaui.net/

For example, here's C# implementation of Visual Basic 6 compiled to WebAssembly https://bandysc.github.io/AvaloniaVisualBasic6/ and source https://github.com/BAndysc/AvaloniaVisualBasic6

And a Solitaire demo https://solitaire.xaml.live/ and source https://github.com/AvaloniaUI/Solitaire

But WebAssembly applications can also manipulate the DOM like JavaScript. Example frameworks that do this:

- https://www.leptos.dev/

- https://dioxuslabs.com/

- https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blaz...

DOM access goes via JavaScript glue code for now. Eventually WebAssembly will get direct DOM access.

You can decide if you're making more of an application or more of a webpage. If you're making more of an application then why not just render to canvas with WebAssembly? And if you're making more of a webpage then why not have WebAssembly manipulate the DOM instead of JavaScript?

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).

Rewrite Muscurdi - Password Manager in Rust with [iced](https://github.com/iced-rs/iced, dioxus and/or tauri

In, my opinion it's good for ambitious projects to have a stable financial foundation. What negative things one project does because of venture capital does not mean another will.

There's no CLA. Dioxus is MIT/Apache-2 licensed.

> How many of the contributors are directly payed for their contributions?

I unfortunately feel like you're asking this in bad faith. Our team is very small, we're very lean, and we have funding sources that aren't just venture. We also have a very active community and people are building new libraries and becoming dioxus contributors every day.

https://github.com/DioxusLabs/dioxus/releases/tag/v0.6.0 (scroll to contributors)

> You still need to access the DOM, which can't be done directly from WASM. Maybe someday it will happen?

You can access the DOM through JavaScript glue. These Rust WASM frameworks do that:

- Leptos: https://www.leptos.dev/

- Sycamore: https://sycamore.dev/

- Yew: https://yew.rs/

- Dioxus: https://dioxuslabs.com/

> Okay, so use canvas instead and do all UI inside WASM?

You can do that too. That's what this VB6 clone written in C# and compiled to WebAssembly does:

- https://bandysc.github.io/AvaloniaVisualBasic6/

- https://github.com/BAndysc/AvaloniaVisualBasic6

> vague "JavaScript limitations"

It's not vague. Despite 28 years of effort optimizing JavaScript, WebAssembly outperforms JavaScript:

- https://nuenki.app/blog/bloom_filters_optimisation

- https://jordaneldredge.com/blog/speeding-up-winamps-music-vi...

- https://www.amazon.science/blog/how-prime-video-updates-its-...