nixos / arch linux / linux distributions

The author praises NixOS primarily for the Nix package manager’s deterministic, functional approach that makes entire operating systems reproducible and roll-backable. They highlight declarative system configuration—covering packages, GNOME extensions, and keyboard mappings—as a single source of truth that avoids the usual system “state drift.” The piece notes NixOS’s stability, predictable six-month cadence, and an unstable channel for experimentation, plus good hardware support (example: an HP laptop). NixOS also enables safe, isolated experimentation via reproducible package shells and declarative build specifications, reducing manual setup and scattered scripts when migrating hardware. This matters for developers, sysadmins, and teams seeking reliable, reproducible environments.

A Hacker News thread highlights enthusiasm for NixOS and nix-based tooling, with users praising reproducible environments and easy local development workflows. Commenters ask how Nix handles apps that auto-update outside the package manager (Discord, Slack, Docker Desktop, JetBrains Toolbox), and one asks whether nix users simply avoid such software. Other replies note practical benefits: using devenv.sh for development environments and the ability to apply quick local patches to upstream packages (example: modifying atuin behavior) and have builds garbage-collected. The thread underscores Nix's power for reproducibility and customization but also hints at onboarding difficulty and friction with software that manages its own updates.

Author praises NixOS primarily for the Nix package manager’s deterministic, reproducible, functional approach that lets them declare and rebuild an entire OS from Nix DSL. They highlight benefits such as a single source of truth for packages and settings (GNOME extensions, key mappings), easy hardware portability, safe experimentation via isolated package shells, stable long-term use with predictable six-month releases and an optional unstable channel for newer software. The declarative model reduces system drift, simplifies upgrades and rollbacks, and makes configuring a new machine or trying new tools low-risk and repeatable. NixOS’s stability and reproducibility are presented as the core reasons to adopt it.

Unified Modules For Your Nixfiles

A year after switching from Arch Linux to NixOS, the author reverted to Arch, citing frequent breakages, large update footprints, and slow builds as reasons. They found NixOS’s declarative model and generation-based rollback useful in theory, but in practice rebuild→fix cycles and unpredictable breakage of components (clipboard, audio, Bluetooth) made maintenance painful. Nix’s approach of storing multiple immutable generations inflates disk usage and forces widespread rebuilds when core libraries (e.g., glibc) change, unless garbage collection is run. Binary caches like Cachix are unreliable for the author’s setup, causing long local compilations — hours versus minutes for Arch’s prebuilt pacman packages. The author favors Arch’s simplicity, faster updates, and predictable behavior for daily desktop use.

A long-time Arch Linux user tried NixOS for a year but reverted to Arch, citing frequent breakage, huge update sizes, and slow compilations. The author found NixOS’s declarative model often demanded repeated config fixes—rebuild → fix cycles—and reported random regressions (audio, Bluetooth, clipboard) after successful builds. Nix’s model keeps multiple generations and installs side-by-side packages, inflating disk use and requiring manual garbage collection, unlike Arch’s in-place replacements. Isolated builds and reliance on binary caches (e.g., Cachix) also led to frequent local compilations that took hours, whereas Arch downloads prebuilt binaries within minutes. The verdict: NixOS is powerful and reproducible but impractical for this user’s daily desktop needs.

  submitted by   <a href="https://www.reddit.com/user/itsdevelopic"> /u/itsdevelopic </a> <br/> <span><a href="https://developic.dpdns.org/blog/why-i-switched-back-to-arch-linux">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1rqpuz3/why_i_stopped_using_nixos_and_went_back_to_arch/">[comments]</a></span>