leptos VS dioxus

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/

Yes, Sciter is definitely pretty close.

We think we can do better CSS support. Sciter has good CSS2 layout support, but only has it's own proprietary equivalent to Flexbox. Our CSS2 support is currently pretty patchy, but we have good Flexbox and CSS Grid support. We also have full support for things like media queries and css variables which I don't believe Sciter supports.

Regarding "just disable the JS":

You can, but then you won't have scripting support. Blitz still has scripting support without JS using https://github.com/DioxusLabs/dioxus which is a react-like UI framework but in Rust.

Related: Dioxus

> Dioxus is a Rust library for building apps that run on desktop, web, mobile, and more.

https://dioxuslabs.com

(Dioxus uses Tauri)

There's also Tauri which https://dioxuslabs.com/ uses.

Dioxus Labs (http://dioxuslabs.com) | Founding Rust Engineer | San Francisco | in-person | Full-time | 125-150k | 0.5-3% equity

I'm Jonathan, the creator of Dioxus (YC S23). Dioxus is a popular crossplatform GUI library for Rust that, imo, is the easiest way to ship apps that are beautiful, fast, and robust.

Dioxus is quite popular, almost 20k stars on GitHub, and we recently raised a sizable seed round from "top vcs." We have a lot of exciting projects on the horizon:

- in-place binary patching for rust hotreloading (http://github.com/jkelleyrtp/ipbp)

- a WGPU powered HTML/CSS renderer (http://github.com/dioxusLabs/blitz)

- experiments with LLM-based component generation (http://github.com/dioxusLabs/dioxus-ai)

- upcoming mobile tooling

- TUI-based devtools for a ruby-on-rail like experience

- a deploy platform for web/desktop/mobile/backend and all the fun that entails...

I'm looking for a founding systems engineer passionate about Rust, WASM, apps, the web, compilers, linkers, and devex - basically someone who's not afraid of anything. Dioxus is a very lean organization and we've been able to move so quickly since we keep our team small and high trust. No annoying standups or corporate bureaucracy. If you want to contribute to OSS, move the needle, and work in a startup that's closer to deeptech with hard problems, this role is for you.

I'm specifically looking for people who are excited by this space and doing this type of work. If you're just looking for a job then this probably isn't the right role for you.

Apply on our yc page or are reach me directly at jon at dioxuslabs dot com

https://www.ycombinator.com/companies/dioxus-labs/jobs/dRPOo...

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).