keyboard-configurator VS crates.io

Many or most of their keyboards are configurable these days. See https://github.com/pop-os/keyboard-configurator

Reported at https://github.com/pop-os/keyboard-configurator/issues/195 - I get a failure from dfu-programmer trying to update using the alternate update method with the keyboard-configurator app (because fwupdmgr won't update it because of the firmware bug that the new firmware addresses).

I found the ticket regarding Fn lock https://github.com/pop-os/keyboard-configurator/issues/159

keyboard-configurator

Good. I bought Darter Pro recently and had to - business as usual under Linux - compile this and tweak that. Via things like their keyboard configurator[1] I was exposed me to Rust's GTK bindings. It wasn't pretty: the mismatch between the obviously object-oriented GTK and Rust which doesn't do (and doesn't want to) OOP was glaring. I understand the appeal of Rust very well, and I'm happy they write their drivers and (parts of) firmware in it, but it's about as fit for OOP-based GUI as Go and Erlang. Which is to say - not very much.

[1] https://github.com/pop-os/keyboard-configurator

That's exactly what it's meant for, but the frontend of the configurator app doesn't seem to list those characters. You may consider opening an issue and relating to this one: https://github.com/pop-os/keyboard-configurator/issues/105

Probably a good issue to open here: https://github.com/pop-os/keyboard-configurator

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.