I have to say the immutability isn’t what got me. It’s that i can propagate changes to all my machines (i have three, with different configurations of work and private users) without fuss. i have one git repo that contains the Config and all i do is git pull && sudo nixos-rebuild switch after i login and it’s done. reinstalling is also somewhat trivial and once the installer is done everything is as i want it to be. which is just bonkers to me. i love it to bits. before i had a super brittle system of dotfiles that regularly broke. nevermore
That does make sense for such use cases, however I feel that archinstall script is also mature enough, allowing you to have config files even. Even w/o them it still has very powerful defaults. I will def give nixos a try in a VM first, as I mostly rely on flatpak and landlock anyways.
I have to say the immutability isn’t what got me. It’s that i can propagate changes to all my machines (i have three, with different configurations of work and private users) without fuss. i have one git repo that contains the Config and all i do is git pull && sudo nixos-rebuild switch after i login and it’s done. reinstalling is also somewhat trivial and once the installer is done everything is as i want it to be. which is just bonkers to me. i love it to bits. before i had a super brittle system of dotfiles that regularly broke. nevermore
That does make sense for such use cases, however I feel that archinstall script is also mature enough, allowing you to have config files even. Even w/o them it still has very powerful defaults. I will def give nixos a try in a VM first, as I mostly rely on flatpak and landlock anyways.