When comparing Nix vs Garuda Linux, the Slant community recommends Garuda Linux for most people. In the question“What are the best Linux distributions for desktops?” Garuda Linux is ranked 16th while Nix is ranked 64th. The most important reason people chose Garuda Linux is:
Uses vram, and a zen kernel.
Ranked in these QuestionsQuestion Ranking
Pro No side effects when building packages
Nix is a purely functional package management system. This means that the act of building a package does not have side effects, such as destructively updating or deleting files that may be used by other packages.
Pro Isolated development environments
Nix allows the creation of project-specific shell and build environments which are isolated from the rest of the system. These environments are defined declaratively to ensure reproducibility.
Pro Can replace docker in some places
Pro Can use multiple versions of the same package
Because of the functional approach it takes, Nix makes it easy for systems to use multiple versions of the same package simultaneously, and ensure that updating or removing a package can't break other packages.
Pro The configuration works on "All machines"
No more of the traditional: "it works on my machine". When it says reproducible, this is the real deal.
Uses vram, and a zen kernel.
The dr460nized KDE theme is awesome.
Pro Easy entrance to Arch Linux
Filled to the brim with lots of quality-of-life changes and optimizations that are simple enough for long-time Windows, long-time Mac users, and Arch newbies to understand. Though, it also leads to bloat or not necessarily helpful extra software. If you're not into the "bloat" added in, try checking out the barebones version, you'll need to know a lot of things bout Arch to fully use barebones.
Pro Highly customized interface
You already have most of the customization done for you out of the box.
Pro Unused RAM is wasted RAM
It takes just a bit more RAM than Manjaro. Edit: This statement is only true if it helps the user and since this could be running on a low end machine this will not.
Con Does not work well for services on non-NixOS systems
When using Nix with anything other than NixOS you can run into difficulties with trying to start up services. For example, you can install docker with Nix, but it won't integrate with the host system's systemd leaving you to handcraft awkward workarounds in order to start the background service that docker requires. This seems like a critical flaw when using Nix on anything that is not NixOS, and it's unfortunate because this affects many of the packages many users would be most interested in using Nix to handle.
Con Steep learning curve
Con Cannot handle filetypes that have different semantics across different versions
While the functional approach that Nix takes is great for sandboxing binary artifacts of packages, it seriously lacks any power in handling configuration files or user data. It's difficult to upgrade and downgrade files where semantics and syntax can change between versions. Especially in Debian/Ubuntu it can cause severe problems where the upgrade process blocks and the user needs to resolve the 3-way merge.
Con Feels slightly over-complicated
Con Needs a lot of RAM
Minimum is 4GB, for most Linux distributions it's 2GB or less.