Late to the party but just read your article and I share a lot of the struggle you said. I don't know if I can fix that by just going back to Arch. I've tried, with different levels of success, a mix between Arch and Nix, but that adds another issue of inter-compatibility of system packages between Arch and Nix which often it's a no-go.
The thing I enjoy the most on NixOS is the ability to make something, then remove it if I don't need it and don't have to worry about config files that are in an unknown-to-me path. But then there is the stateful aspect of the programs I used that I have to keep track of...
I only got started with NixOS a couple of weeks ago and I must agree. I would never consider running Nix on my daily Desktop machine (I'm using Arch BTW). It's more work and hassle than it's worth it.
OTOH I just set it up as the base for my new DIY NAS. There it is limited to just the bare minimum of bringing the system up and providing some core services (including Samba). And for this I found Nix' declarative approach quite good. I can easily restore the root system from the backed up config alone.
Everything else will be handled by Docker compose stacks outside the Nix eco system (stored on the RAID).
I had the opposite experience. I started using it as a daily driver around 10 years ago and could never to back to anything else. It's just super solid and once you have it configured it just works forever. I agree that the learning curve is pretty steep, especially if you want to use something that's not in nixpkgs but those things are vanishing day by day.
Yeah, for all the blog posts about quitting NixOS there's plenty of us who continue using it.
I don't think it's just the steep learning curve though, I think it's just not for everyone. You _have_ to enjoy side quests where you dive deep into hairy problems, and effectively be willing to front load effort into setting up an environment so that it works well for you in the long term.
Can you elaborate on what were the friction points? I migrated from Arch to Nix several years back because I found maintenance to be incredibly easy and it also allows me to test things without fear. Arch and other imperative distros are still superior for some workflows, but you can always run something imperative inside Nix like FHSEnv or DistroBox. Nix is also available in Arch extra, so it's also possible to do this the other way round, with Arch as a host.
For me (recent NixOS user), it's mainly two things:
- for every configuration item in the software I use, I basically need to learn the way to NixOS-configure it (assuming I don't want to raw-configure everything)
- experimentation is onerous (unless there are workflows I don't know), for example: messing with my sway config requires rebuild switches
I'm not bailing (yet?) but the "ergonomics", well, don't feel ergonomic.
> I would never consider running Nix on my daily Desktop machine (I'm using Arch BTW). It's more work and hassle than it's worth it.
How much of this is really just unlearning what you have learned, and needing to internalize the Nix way of doing things which may allow more flexibility in the end?
There once was a post "The curse of Nix", or something like that, with the main idea that Nix isn't perfect, but once you tried it, everything else seems even worse.
For the first six months of using NixOS I couldn't run anything but a browser (I'm exaggerating a bit), yet all attempts to get back to Arch failed for me.
Now it's been over 4 years of having NixOS on all my computers, from Laptops to ARM SoCs driving my speakers. And so far I've no desire to try anything else.
Moreover, when I was looking for new a NAS, I specifically picked a model allowing me to run an OS of my choice – so alien and unappealing seemed to me the concept of configuring things not through Nix.
To each their own. But the curse of Nix is a real thing. And if the OP doesn't try at least running Nix on Arch, I'd say, he just doesn't appreciate Nix benefits in the first place.
For me, my computer is a tool that I need to just work. Therefore I understand the frustration of occasionally fighting Nix to get things to work right.
For the same reason, I don't think I will ever move off of Nix again. Once something works, it works reproducibly. I can always go back to a known-good state if I break something. This gives me freedom to experiment that I would otherwise not permit myself for fear of breaking an important workflow.
I've dabbled in NixOS and come to many of the same conclusions. The learning and troubleshooting overhead just isn't there yet (for me). I appreciate the concept and I do think declarative configurations do have a place in the near future, especially in corporate environments. I'll probably give it another go in a year or so to see if it's gained any more polish.
Working with sandboxed/containerized/nixos stuff is like eating with chopsticks, except you are holding the chopsticks with another set of chopsticks. For a brief moment it is interesting, then it becomes a nuisance, and soon it is even painful to watch others do it.
I had a similar experience with NixOS and eventually gave up. I liked the idea of NixOS but I do lots of weird things off the beaten path and was constantly troubleshooting why things wouldn't work.
For me, building/running environments in containers is the least amount of friction.
The leaky abstraction argument is itself leakly. Yes, it would be nice if we weren't putting lipstick on a Unix pig, but Nix never promised the underlying thing wasn't Unix. It sounds to me like he is moving the goalposts.
If he wanted to run a bunch of shitty precompiled binaries from NPM for work, I would simply create a normie Ubuntu container or whatever and use that. There is no reason one's personal configuration should have to kowtow to such work things — it's probably better to have that sort of work-life separation anyways.
Right, the problem is that this leaky abstraction effectively now requires you're both good at Nix and good at fixing whatever tool it is that is refusing to work with Nix. That usually means diving deep into build systems, code that makes wrong assumptions, and probably other hairy topics. In return you do get a state of the art system, but you very often need to put in work you otherwise wouldn't need to.
I don't mind that because that's how my brain is wired, but there's plenty of people who don't give a shit and Just Want Things To Work Out Of The Box. Nix(OS) is certainly not for everyone.
I don't see what the problem is. What Nix is doing is far more transparent than the article's preferred solution of Docker images. While Docker images are entire distros crammed into a binary blob, Nix derivations are inspectable and customizable. Nix uses standard mechanisms to configure software, like config files and environment variables. It really isn't black magic.
Also contrary to popular opinion, Nix configs are actually easier to comprehend and maintain than configs written in Chef, Ansible, or Kubernetes. Having a proper language for describing large and complex pure data helps.
Readit News
The thing I enjoy the most on NixOS is the ability to make something, then remove it if I don't need it and don't have to worry about config files that are in an unknown-to-me path. But then there is the stateful aspect of the programs I used that I have to keep track of...
OTOH I just set it up as the base for my new DIY NAS. There it is limited to just the bare minimum of bringing the system up and providing some core services (including Samba). And for this I found Nix' declarative approach quite good. I can easily restore the root system from the backed up config alone.
Everything else will be handled by Docker compose stacks outside the Nix eco system (stored on the RAID).
https://www.splitbrain.org/blog/2025-08/03-diy_nas_on_nixos
I don't think it's just the steep learning curve though, I think it's just not for everyone. You _have_ to enjoy side quests where you dive deep into hairy problems, and effectively be willing to front load effort into setting up an environment so that it works well for you in the long term.
- for every configuration item in the software I use, I basically need to learn the way to NixOS-configure it (assuming I don't want to raw-configure everything)
- experimentation is onerous (unless there are workflows I don't know), for example: messing with my sway config requires rebuild switches
I'm not bailing (yet?) but the "ergonomics", well, don't feel ergonomic.
How much of this is really just unlearning what you have learned, and needing to internalize the Nix way of doing things which may allow more flexibility in the end?
For the first six months of using NixOS I couldn't run anything but a browser (I'm exaggerating a bit), yet all attempts to get back to Arch failed for me.
Now it's been over 4 years of having NixOS on all my computers, from Laptops to ARM SoCs driving my speakers. And so far I've no desire to try anything else. Moreover, when I was looking for new a NAS, I specifically picked a model allowing me to run an OS of my choice – so alien and unappealing seemed to me the concept of configuring things not through Nix.
To each their own. But the curse of Nix is a real thing. And if the OP doesn't try at least running Nix on Arch, I'd say, he just doesn't appreciate Nix benefits in the first place.
Probably 6702, but can't verify right now.
For the same reason, I don't think I will ever move off of Nix again. Once something works, it works reproducibly. I can always go back to a known-good state if I break something. This gives me freedom to experiment that I would otherwise not permit myself for fear of breaking an important workflow.
I've dabbled in NixOS and come to many of the same conclusions. The learning and troubleshooting overhead just isn't there yet (for me). I appreciate the concept and I do think declarative configurations do have a place in the near future, especially in corporate environments. I'll probably give it another go in a year or so to see if it's gained any more polish.
For me, building/running environments in containers is the least amount of friction.
If he wanted to run a bunch of shitty precompiled binaries from NPM for work, I would simply create a normie Ubuntu container or whatever and use that. There is no reason one's personal configuration should have to kowtow to such work things — it's probably better to have that sort of work-life separation anyways.
I don't mind that because that's how my brain is wired, but there's plenty of people who don't give a shit and Just Want Things To Work Out Of The Box. Nix(OS) is certainly not for everyone.
Also contrary to popular opinion, Nix configs are actually easier to comprehend and maintain than configs written in Chef, Ansible, or Kubernetes. Having a proper language for describing large and complex pure data helps.