When comparing yay vs paru, the Slant community recommends yay for most people. In the question“What are the best AUR helpers for Arch-based Linux distributions?” yay is ranked 1st while paru is ranked 6th. The most important reason people chose yay is:
It's written in Go so it is fairly easy to add features or tweak this amazing tool.
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 Based on the design of yay
You can simply alias yay=paru if you switch from yay.
Pro Fast
Paru is faster than yay.
Pro Actively maintained
With the main yay developer stepping away from yay, paru is more actively maintained than yay.
Pro Saner defaults than yay
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.