When comparing Nix vs PCLinuxOS, the Slant community recommends PCLinuxOS for most people. In the question“What are the best Linux distributions for desktops?” PCLinuxOS is ranked 38th while Nix is ranked 75th. The most important reason people chose PCLinuxOS is:
The distribution is continually updated, so there's no need to install OS upgrades by hand.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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.


Pro Rolling release
The distribution is continually updated, so there's no need to install OS upgrades by hand.

Pro Stable
PCLinuxOS is designed around stability.

Pro Multiple desktops available
Mate, LXDE, and KDE desktops are available.

Pro Can remaster the boot DVD
PCLinuxOS has built in tools for remastering bootable DVD into a copy of current install.

Pro Excellent hardware compatibility
Comes with nVidia drivers out of the box. Important if the PC has an nVidia chipset. Most Debian based distros don't have nVidia drivers available at install time.
LXDE version works well with older hardware.
Cons
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 Installation fails most of the time, error messages, and hard to go to full screen in virtual box

Con Uses RPM packaging system
Uses the RPM packaging system with APT, rather than the more popular DEB packages.
