dnf VS berry

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.

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.

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

dnf for Fedora and Redhat Linux.

First things first, I made two crucial infrastructure changes. I bid farewell to Yarn and embraced pnpm, the package manager known for its speed and efficiency. With its three-stage installation process, pnpm swiftly handled dependency resolution, directory structure calculation, and linking dependencies.

If you use the Yarn Package Manager instead of npm and run the command yarn upgrade-interactive --latest, you'll see a color-coded legend that indicates the likelihood of a package update breaking your code:

3. A package manager: This is a tool that helps you manage dependencies (libraries and frameworks that your code depends on). The most popular package managers for JavaScript are npm (comes with Node.js) and Yarn.

As a developer, I have used Yarn as an alternative to NPM for managing packages and dependencies in my Node.js projects. One of the things that I love about Yarn is its faster installation times compared to NPM. Yarn's caching mechanism ensures that packages are only downloaded once, which means that subsequent installations are much faster. Additionally, Yarn's parallel installation process allows multiple packages to be installed simultaneously, which further improves installation times.

To run this project locally, you will need to have Node.js and npm (or Yarn) installed on your machine.

For a package manager I usually use yarn instead of npm. But npm is fine nowadays too.

If you prefer to set up the project on Vanilla JS, remove --typescript tag from the command. Notice, that Yarn package manager is the requirement to create a project.

A package manager lets you install, update, and manage third-party packages. Popular package managers: npm (built into Node.js), Yarn, pnpm.