Nix is great but not the saving grace I thought it would be. I daily it. Like it. Run cinnamon coming from Mint. But to be fair. It takes real effort and time to setup your config file, comment it thoroughly and then master the system. Once it’s fully automated backups and all you can hop machine to machine and it’s like you never left your OG machine. There’s pros and cons for sure.
If there was a simple Debian based distro that I could declaratively manage via a single config file, I think I’d try it. I.e. not using Puppet or Chef that can only bootstrap a system state, but something to truly manage a system’s entire life cycle, including removing packages and anything littering the system file tree. But since there isn’t, I’m using NixOS instead.
Having a DSL to declare my entire system install, that I can revision control like any other software project, has been convenient for self documenting my setup and changes/fixes over time. Modularizing that config has been great for managing multiple host machines synchronously, so both my laptop and desktop feel the same without extra admin work.
Nixpkgs also bolsters a lot of bleeding edge releases for the majority of FOSS packages I use, which I’m still getting used to. And because of how the packaging works, it’s also trivial to config the packages to build from customer sources or with custom features. E.g. enabling load monitoring for Nvidia GPUs from btop that many distros don’t ship by default.
In my experience the Arch people are the sane ones and the NixOS people are the young cult evangelists nowadays. I use Arch btw
Nix is great but not the saving grace I thought it would be. I daily it. Like it. Run cinnamon coming from Mint. But to be fair. It takes real effort and time to setup your config file, comment it thoroughly and then master the system. Once it’s fully automated backups and all you can hop machine to machine and it’s like you never left your OG machine. There’s pros and cons for sure.
What is making NixOS so passionated about it? Is there something very special in NixOS that we are missing in Arch?
If there was a simple Debian based distro that I could declaratively manage via a single config file, I think I’d try it. I.e. not using Puppet or Chef that can only bootstrap a system state, but something to truly manage a system’s entire life cycle, including removing packages and anything littering the system file tree. But since there isn’t, I’m using NixOS instead.
Having a DSL to declare my entire system install, that I can revision control like any other software project, has been convenient for self documenting my setup and changes/fixes over time. Modularizing that config has been great for managing multiple host machines synchronously, so both my laptop and desktop feel the same without extra admin work.
Nixpkgs also bolsters a lot of bleeding edge releases for the majority of FOSS packages I use, which I’m still getting used to. And because of how the packaging works, it’s also trivial to config the packages to build from customer sources or with custom features. E.g. enabling load monitoring for Nvidia GPUs from
btopthat many distros don’t ship by default.