druid VS crates.io

For GUI applications, the story is mixed. There are several GUI frameworks in active development, but nothing as polished and battle-tested as Electron for TypeScript. There are bindings to GTK, but they're cumbersome to work with, and I wouldn't recommend it to a Rust newbie. There's also Tauri, which is a bit like Electron and lets you write the GUI in HTML/CSS/JS and the business logic in Rust.

Concerning GUI frameworks, the most common ones are druid, egui and iced. All three of them run native and on the Web.

Going to give a shoutout to druid. I've recently tried it with the Lapce editor and it's just so smooth, fast and works so well for a pre-alpha app.

As iced and egui were difficult for me, i started with druid.

There is Iced which is used by system76 in Pop!_OS, Druid [DISCONTINUED], GTK-rs, Relm, Azul and Tauri. Personally I would use Tauri for its speed using the OS's native web render, documentation of use with things such as Sveltekit and the ability to make UI's using JS, CSS and HTML. Tauri similarly to Electron whilst being far faster. But its up to personal preference really. There aren't any solid "go to" options at the moment.

Druid should be good for most cases, it has a lot of built-in widget for the UI, you can even make a custom widget with a canvas-alike painting API.

Druid, which is a Rust-native UI toolkit for building desktop applications targeting Windows/macOS/Linux/OpenBSD/FreeBSD, has a new version out - v0.8.

There's a memoize View node in the previous iteration of the Xilem prototype, but it hasn't made it in to the current branch yet. That sounds like what you're asking, but it's possible I'm missing something.

You can use GTK from Rust. But the Rust native ones aren't really there yet. [Iced](https://github.com/iced-rs/iced) which has been picked up by System76 and [Druid](https://github.com/linebender/druid) (and it's next gen version [Xilem](https://github.com/linebender/xilem)) are the ones to watch, along with Dioxus which is the main post here.

I'd expect there to be something useable by the end of 2023.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.

So this is my question: Which way was the right to find it out? There is no info about this feature on crates.io. I also have no clue what exactly it does and why it is named rwh_05.

Rust does it so much better with https://crates.io . I don't know why Go can't (or won't) do something similar.