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
Can you give an example of what installing a tool and using it looks like? Nix is very different from other tools I understand.
oh yeah, Nix is powerful and also has quite a steep learning curve compared to other tools, but you can adopt gradually, some utility of Nix I can list out here:
- experimenting with packages with
nix-shellwhen you are not sure if u want to install - use it just like other package managers like
homebrew,yay, etc withnix-env(imperative way, not really recommended by the community) - manage the entire dev environment with
home-managerand nix flake. If you use macOS or nixOS, you can even manage your OS settings (on macOS usesnix-darwin) - manage dev dependency on project level with
direnv+ nix. for example, you don’t want to install python on your machine, but only want it active in the repo you’re working on, u can declare it inside the repo
here is my tutorial a while ago, I still don’t write the next part but this might be a good start for u. And here is my personal setup using nix and home-manager
- experimenting with packages with
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?
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.
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.
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.
Nice. Do you think it would be feasible to replace Nix-the-language with something more … how do I say it … conventional?
I mostly copy from other people’s config, not much learning at all. Heard that Guix is a good too if you only use linux, but it doesn’t have nonfree softwares right?
Guix indeed doesn’t include nonfree software by default, but you can add the nonguix channel which does have it.
