dnf VS crates.io

I just use dnf-makecache.service to handle background metadata syncs. Just modify the dnf-makecache.timer to manage when these occur.

https://github.com/rpm-software-management/dnf/pull/1879

However its o my going to work on rhel 10 or anything that has very very up to date DNF version.

Sure. Raise a bug report. Asking nicely on Reddit isn't going to make it happen.

I'm not sure, I'm not a dnf developer. It was implemented in C++, so it would probably have to be done differently in version 4. I belive dnf development is focused on version 5 right now, so adding features to version 4 is probably not a high priority. It would be nice to see it in version 4 so it could be added to current versions of RHEL and Fedora, but time is a finite resource. Perhaps you could implement and send a pull request, or at least file a bug to discuss it upstream?

dnf uses python only for command line functionality. Its core part, libdnf, is written in C++. However yes, dnf in my experience is still significantly slower than apt and pacman.

Lots of people use python apps and not know about it. I don't get where the idea that it's complicated comes from. You run them the same way as everything else. For example if you use anything redhat-based you're running a python app (https://github.com/rpm-software-management/dnf). If you're running any desktop environment, you're likely using at least one python app or something with python scripting embedded.

Of course they also changed the default fedora dnf.conf to make it include best=False, so there was no change, except users can simply delete this line in dnf.conf to enable best.

Rust: crates.io

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

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