crates.io VS cxx-qt

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.

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

It's more that crates.io gets frustrating. When you end up with a pile of duplicated 3rd party transitive dependencies. Or find that something you foolishly chose as a dep has been abandoned. Or both.

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.

Are there any crates that do this? If yes, I'd love to know about them, however, I'm doubtful as I've searched crates.io and found no luck.

My employer, KDAB, is building an excellent Rust binding for Qt: https://github.com/KDAB/cxx-qt

You can use cxx-qt or qmetaobject-rs. Or use Slint

Rust has several Qt bindings. The most popular are Ritual, CXX-Qt, and qmetaobject. Ritual is not maintained anymore, and qmetaobject doesn't support QWidgets. So CXX-Qt is our best bet for now.

We're getting closer, but you're still likely to run into missing features in CXX-Qt at this point. If you do, please report it on GitHub!

This is no longer required in CXX-Qt as of this week (https://github.com/KDAB/cxx-qt/pull/428). Next release coming soon.

From my understanding KDAB isn't trying to "replace" Qt. They're working on cxx-qt to make using Qt and Rust together much easier.

I second this. I wrote an internal Qt/QML app that ran on Windows, Linux, Android, and Raspberry Pis. We had ~20 Raspberry Pi's running this app in kiosk mode. If only KDAB/cxx-qt[1] were ready there, I would have done as much as possible in rust .

- [1] https://github.com/KDAB/cxx-qt/

> I have searched high and low for something better, here is one rabbit hole: https://www.areweguiyet.com

I'm very interested in the KDAB/cxx-qt path from that page: https://github.com/KDAB/cxx-qt

Once they get Arm & Android coverage, that'll be my go-to solution. Rust for all business logic and remote synchronization. Qt/QML for display with accessors into the Rust model.

I'm working on it. :)