When comparing yay vs RPM (RPM Package Manager), the Slant community recommends RPM (RPM Package Manager) for most people. In the question“What are the best Linux package managers?” RPM (RPM Package Manager) is ranked 5th while yay is ranked 8th. The most important reason people chose RPM (RPM Package Manager) is:
This makes maintenance and support easy.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to add features
It's written in Go so it is fairly easy to add features or tweak this amazing tool.
Pro Intuitive CLI
Yay's commands and output make sense for anyone used to the pacman package manager.
Pro Written in Go
The compiled program is snappy while the source is easy to read.
Pro Available as a precompiled binary
Both yay and yay-bin are in the AUR, the latter of which doesn't require any dependencies or compilation, making installation and updates quick and painless.
Pro Yogurt interactive mode
Write package name without keys [yay <packagename>] to enter interactive mode.
Pro Doesn't rebuild already-installed apps like Trizen
Pro Easy to create packages on non-rpm based distros
This makes maintenance and support easy.
Pro Follows the UNIX philosophy
It only does one thing and that well.
Pro Part of LSB
It is part of the Linux standard base.
Pro Very easy to create packages
It is very easy to create packages for it, you just need a small spec file.
Pro Standard archives
RPM packages are simple cpio archives that have additional compression support.
Pro Much more advanced than apt
Cons
Con Written in Go
Running a Go program requires the Go runtime. Go is also a garbage collected language, so the program isn't as responsive as it could be.
Con No interaction
RPM does not support user interaction upon install.
Con Many forks
Currently there exist rpmv4, rpmv5 and distribution specific forks like Mandrake's urpm.
Con Plenty of different frontends
Almost any rpm distro has its own frontend for rpm there is zypper, yum, apt-rpm, dnf, poldek and many more.
