dnf VS Chocolatey

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.

Package managers – With tools like Scoop or Chocolatey, installing dev tools on Windows feels almost like using apt or brew.

While the ArchWSL and Fedora WSL at MS Store may seem great at first before installing, these distros have often showed compatibility issues and sometimes very weird bugs; even conflicts with scoop or chocolatey apps.

Chocolatey Windows software management solution, we use this for installing Python and Deno

Authenticating with Kyma is a (in my opinion) unnecessary challenge as it leverages the OIDC-login plugin for kubectl. You find a description of the setup here. This works fine when on a Mac but can give you some headaches on a Windows and on Linux machine especially when combined with restrictive setups in corporate environments. For Windows I can only recommend installing krew via chocolatey and then install the OIDC plugin via kubectl krew install oidc-login. At least for me that was the only way to get this working on Windows.

On a Windows machine, you can use Chocolatey by running the command.

I've used WSL2 and GHC/Nix--worked without any issues. However, there is Chocolatey: https://chocolatey.org/

For OSX there is homebrew or pyenv (pyenv is another solution on Linux). As pyenv compiles from source it will require setting up XCode (the Apple IDE) tools to support this which can be pretty bulky. Windows users have chocolatey but the issue there is it works off the binaries. That means it won't have the latest security release available since those are source only. Conda is also another solution which can be picked up by Visual Studio Code as available versions of Python making development easier. In the end it might be best to consider using WSL on Windows for installing a Linux version and using that instead.