This might just be the best thing that happens in tech (for me) all year.
I daily drive debian just because boring and reliable. However, fancy package managers like flatpak and appimages and nix have made debian much more vibrant - it’s easy to install new versions of things now.
That said, nix package manager on debian is just freakin amazing. Being able to just nix-shell -p <obscure cli tool> and exit when I’m done with it is magnificent.
That’s the gateway drug anyway. The nix based home-manager is pretty cool.
While I’ve been tempted to jump in with NixOS my experience with nix packages and home-manager has felt kind of bleeding edge or experimental. Loads of things that don’t work as intended on debian.
A sophisticated well funded user base like a federal government has really good implications for the stability of the project in the future. I’m really stoked about this.
NixOS is great, but it definitely breaks things. It’s the way it works, though, not whether the software is bleeding edge. Nix lets a package specify its own dependencies, even if those dependencies conflict with those of another package. It does this by breaking the traditional POSIX file system structure that many programs assume they can depend on. It puts all sorts of things where they “don’t belong”, and then uses a small army of environment variables, scripts, and symlinks to stitch it back together so that no individual package realizes what happened. If you only use software from the package manager, this is often (but not always) seemless, but if you download stuff from the web, none of the system libraries it traditionally expects are there. Likewise, if you’re using Nix alongside something like Debian’s apt, I wouldn’t be at all surprised if the two package managers doing things in two different ways causes some issues that are hard to interpret to the uninformed.
This might just be the best thing that happens in tech (for me) all year.
I daily drive debian just because boring and reliable. However, fancy package managers like flatpak and appimages and nix have made debian much more vibrant - it’s easy to install new versions of things now.
That said, nix package manager on debian is just freakin amazing. Being able to just
nix-shell -p <obscure cli tool>andexitwhen I’m done with it is magnificent.That’s the gateway drug anyway. The nix based home-manager is pretty cool.
While I’ve been tempted to jump in with NixOS my experience with nix packages and home-manager has felt kind of bleeding edge or experimental. Loads of things that don’t work as intended on debian.
A sophisticated well funded user base like a federal government has really good implications for the stability of the project in the future. I’m really stoked about this.
NixOS is great, but it definitely breaks things. It’s the way it works, though, not whether the software is bleeding edge. Nix lets a package specify its own dependencies, even if those dependencies conflict with those of another package. It does this by breaking the traditional POSIX file system structure that many programs assume they can depend on. It puts all sorts of things where they “don’t belong”, and then uses a small army of environment variables, scripts, and symlinks to stitch it back together so that no individual package realizes what happened. If you only use software from the package manager, this is often (but not always) seemless, but if you download stuff from the web, none of the system libraries it traditionally expects are there. Likewise, if you’re using Nix alongside something like Debian’s apt, I wouldn’t be at all surprised if the two package managers doing things in two different ways causes some issues that are hard to interpret to the uninformed.