Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Nix vs Slackware, the Slant community recommends Slackware for most people. In the question“What are the best Linux distributions for desktops?” Slackware is ranked 5th while Nix is ranked 75th. The most important reason people chose Slackware is:
Uses stable, plain-vanilla packages from upstream.
Specs
Question 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 Stable
Uses stable, plain-vanilla packages from upstream.
Pro Strong adherence to UNIX Principals
Pro Ideal to learn more of Linux
Follows the original Linux roots. It still sees Linux as a free clone of UNIX so the distribution tries to be UNIX-like.
Pro Package management
Uses standard tar archives with shell scripting as packages.
Pro One more distro which is init based
Some users don't like to install systemd based distros because they increase booting and processing speed.
Pro Oldest surviving Linux distro
Besides Debian (which was first released in August 1993), it is the oldest still maintained Linux Distribution and was first released in July 1993.
Pro Super fast
Pro No systemd
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 Not user-friendly
It is made to be KISS (keep it simple, stupid), so you have to do everything by hand.
Con Large size live ISO
One needs to vain 3GB+ data for downloading one slackware ISO.
Con Narrow repos
Doesn't offer the same amount of options as other distros do.
Con Niche/small community
Slackware is its own niche and has a small community.
Con Very slow release cycle
Hasn't updated in 3+ years.
Con Dependency issues
When it comes to dependencies, Slackware shows more issues than many other distros.
