Rendered at 23:33:10 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
forgetbook 24 hours ago [-]
"What I had been calling “Linux knowledge” was actually two different things bundled together: understanding of how systems work, and familiarity with where things live on a particular filesystem. The first transfers perfectly to NixOS. The second becomes largely irrelevant, and whilst that felt like a loss at first, I now think it is fine. Knowing that configuration files live under /etc is useful context, but it is not deep understanding. Deep understanding is knowing what the configuration does and why, and that knowledge is entirely portable."
Particularly:
>> "familiarity with where things live on a particular filesystem."
Taken in context with mightyiam's quote:
>> "because I get to keep it, share it across multiple computers, "
It seems to me like a primary advantage of NixOS is that familiarity with where things live on your particular filesystem is made to be portable across machines, and not a constant beachead.
DemiGuru 5 hours ago [-]
Call me naive, but why not natively run the Nix package manager side-by-side with pacman. This allows one to safely use tools like Home Manager to manage their user environment and dotfiles declaratively while leaving the core Arch Linux base completely untouched.
OhSoHumble 23 hours ago [-]
For me, it was easier to just continue to use Ansible for machine reproducibility. I really like the thought behind Nix but I felt like I needed to elbows deep in it 24/7 to really grok it. And if I stopped looking at Nix for 6 months, then that knowledge just disappeared. I migrated away from NixOS for my homelab because I would come back to flakes I had written and not understand how anything worked and couldn't be bothered to relearn. I know that Ansible and Nix can sometimes be apple and oranges but I know that I can come back to a playbook and understand what it does even if I haven't touched Ansible for years.
willx86 13 hours ago [-]
Hyprland will bite you in the bum soon
They changed their config to lua, so no more hyprland.conf good thing nix has rollbacks !
Maybe migrate sooner rather than later
gausswho 12 hours ago [-]
I decided to get ahead of this and yesterday made the migration. Or rather I should say, asked GPT 5.5 to. I estimate that I have a fairly complex configuration, and I had some bumps - some were preexisting problems - but ultimately it went pretty smooth. I'm glad we're over the days of binde, bindd, bindl, and other magic-letters-at-end-of-commands, but there are cases were it feels verbose without benefit.
tazard 18 hours ago [-]
Not really touched on here, but one thing I found very useful in switching to nix is having your entire system defined in a single repo opens it up for very nice agentic setups. Claude code can now configure my whole system, debug my gpu issues, install software etc, and I can simply git diff to inspect the changes and apply if I agree. On arch sometimes Bluetooth not working or my fingerprint scanner not working becomes some hours of debugging, now I can solve these issues trivially, and if it doesn't work I can restore to an earlier point instead of trails of attempts left through my imperative system
Particularly: >> "familiarity with where things live on a particular filesystem."
Taken in context with mightyiam's quote: >> "because I get to keep it, share it across multiple computers, "
It seems to me like a primary advantage of NixOS is that familiarity with where things live on your particular filesystem is made to be portable across machines, and not a constant beachead.
They changed their config to lua, so no more hyprland.conf good thing nix has rollbacks !
Maybe migrate sooner rather than later