[rgoulter]

I think it's worth adding that NixOS probably will require more effort to use than the "it just works" UX that GP seems to be wanting.

Getting familiar with nix can take some time. e.g. figuring out how to write a Nix package if there's not a package already can be difficult.

When things work in NixOS, it really does feel very nice to know you have a declared config (so that you don't have to worry about what changes you made). When things don't work in NixOS, it may be quite demanding/challenging to fix.

[colordrops]

You could say the same about Linux in general. It does takes some time to really get comfortable with the complex surface area of the system, but once you do, the benefits are tremendous and without doubt. Same goes for programming languages, driving a car, learning guitar, etc. I don't think people really understand the fundamental shift of moving to declarative config. It's absolutely worth the cost of admission and offers "superpowers" for many of us. Others may not need or desire these powers, and Ubuntu or Windows or MacOS will do the job.

[rgoulter]

Ah, sure. I think it's worth the cost; but I also think it's not a cost everyone wants to pay.

In a way, I think most of the "I tried Nix/NixOS but didn't stick with it" comments are about its learning curve.

I'd make comparisons to other tools: VSCode does the job pretty well without having to learn anything, but many people will learn tools like vim, & emacs. (The latter isn't just out of legacy; kakoune & helix seem pretty neat).

Still, I'd gate these power-user tools behind "you need to take the time to learn them", rather than a general recommendation.