Nix & NixOS | Reproducible builds and deployments
nixos.org
Nix is a tool that takes a unique approach to package management and system configuration. Learn how to make reproducible, declarative and reliable systems.

I think the main pain point of distro hopping is learning a new package manager, I discovered Nix a while ago, it works on every single OS, has the biggest package repo out there. I replaced Homebrew on my mac with it. If this piques your interest, give it a go. Later, you can integrate with Home-manager to manage all of your program config to have a reproducible dev environment on any machine, as described in the tutorial here.

The catch is it’s really advanced and got steep learning curve. You can adopt gradually tho. Just get started with nix-shell and nix-env

  • 𝕊𝕚𝕤𝕪𝕡𝕙𝕖𝕒𝕟
    2•1 year ago

    I use dnf and flatpak on Fedora and I’m pretty satisfied. What is the killer feature of Nix that would make it worth learning how to use it?

    • JackbyDev
      6•1 year ago

      To add to the other comment, Nix really strives for true and actual reproducibility. Someone please correct me if I’m wrong, but my understanding is that even in builds it uses fake timestamps to ensure if a timestamp is in the resulting binary it doesn’t mess up the hash of it. They really do try to go a step beyond others in the realm of reproducibility it seems.

    • Howard DoOP
      5•1 year ago

      the problem nix trying to solve is reproducible build, which means from a single config file you can migrate to any machine and have the same environment, auto install and dot files. While other package manager install in a imperative way, which means you have to call the install command on every package you need and you have to remember it. That’s the basic difference. You can consider trying it if you see it’s worth it. It’s harder than any other package manager I know, but it solves a different problem.

    • @Buttons
      4•1 year ago

      A less theoretical advantage is that it can create the exact same environment on both Mac and Linux, and in neither case does it need to replace your primary package manager.

      If the whole team is using nix, then the “setup” section of the readme just says “use nix-shell”[1] and that is more than enough for everyone.

      [1]: I can’t remember if nix-shell is the right command, or not, but in theory nix can create an exact environment on every machine with one command.