3 ms·
Something that perhaps detracts from the positives of NixOS is that a lot of the tools that have the biggest issues with the need/difficulty of dealing with mul
by dangus 5y ago
Something that perhaps detracts from the positives of NixOS is that a lot of the tools that have the biggest issues with the need/difficulty of dealing with multiple versions and environments have long ago come up with their own solutions to the problem.
Python has pyenv, NodeJS has nvm, Terraform has tfenv, and the list goes on.
Then if you're running on a server/VM/cloud, it seems to me that you should be treating your systems as cattle instead of pets. I never update packages on servers, I build a new image/instance, test it, and replace the server.
I wonder if some of the benefits of NixOS were either solutions looking for problems or solutions where better solutions rose to prominence.
I haven't even started talking about containerization, either!
- Filligree 5y ago> Then if you're running on a server/VM/cloud, it seems to me that you should be treating your systems as cattle instead of pets. I never update packages on servers, I build a new image/instance, test it, and replace the server. I have six or so servers, all of them configured differently. Not completely differently; they share some configuration. But not very similarly either. They're pets. They have a lot of state. Backups are running, but I certainly don't want to reinstall them. Despite being pets, I still want to do as little work to manage them as I possibly can. NixOS is great in this scenario.
- jonringer117 5y ago> Python has pyenv, NodeJS has nvm, Terraform has tfenv, and the list goes on. Nix makes these all largely irrelevant, in a consistent way. If anything I would say this supports nix's usage. > Then if you're running on a server/VM/cloud, it seems to me that you should be treating your systems as cattle instead of pets. I never update packages on servers, I build a new image/instance, test it, and replace the server. You can do this is nix as well. You can take a configuration.nix and ship it as a version controlled file, an iso image, pxe boot image, ami, vhd, or other formats. > I wonder if some of the benefits of NixOS were either solutions looking for problems or solutions where better solutions rose to prominence. I don't think so: https://blog.flyingcircus.io/2016/05/06/thoughts-on-systems-management-methods/ https://blog.flyingcircus.io/2016/05/06/thoughts-on-systems-... > I haven't even started talking about containerization, either! Containers generally take an impure process and create a "snapshot-in-time". Nix allows you to "hydrate" your configuration in a reproducible and repeatable fashion. OCI images can only really be layered, can't be composed, and commands like `sudo apt-get install` or `pip install` also makes the runtime behavior dependent on when the image was created.