Okay sure, but that's like trying to use iOS and then saying it's too restrictive. NixOS is pretty clear on what it offers and what it can do.

My personal nixos config

dude, I learned and used NixOS for 2 years and I found it incredibly challenging as some of the documentation is fragmented to the point where you have to delve into several hundreds of others configurations to fix singular problems. Some issues are actually impossible to solve (unless you have months of time off and proficiency with Nix) as NixOS is not FHS compliant.

In addition, good luck with finding what you want as sometimes it's unsearchable as the devs decided not to distinguish the 3 from each other.
Why? I have no idea.

I haven't even mentioned Nix Flakes which is it's own level of complexity due to it's experimental but recommended status by the community.

Perhaps it's a skill issue but I feel that I've spent my 2 years of due diligence to know that it's still quite rough on the edges.

At this point I'm personally moving to Arch.
I'll be experimenting with Gentoo sometime in the near future but at this point it's very unlikely I'll ever revisit Nix and NixOS especially since Valve is doing fantastic work in collaboaration with the Arch Linux devs.

For all I've said above

Because reading the docs is too hard for an imbecile?

Please reconsider before posting future antagonistic and abbrasive comments as it does no favors to you nor the community and only paints a target on your back👍

Nix and NixOS are not easy beasts to tame as advanced help is sparce and individual challenges can be quite niche such that help cannot be readily found.

I'm gonna be honest, I use NixOS, but the docs fucking suck, and a number of things are just broken in nixpkgs. For instance, I recently discovered the structuredExtraConfig option for patching the kernel straight up does not work. This means you cannot unset any kernel options, which means some kernel patches won't work unless you manually supply the entire kernel config.

EDIT: what's even more annoying about it not working is that it fails to apply silently. In other words, your kernel tries to compile and then an hour later it fails because your config changes weren't applied.

If you drive a car, have you read the entire owner's manual for every car you've owned? If you're a homeowner, how about your hvac system? What about your system shell? Your compiler(s)?

At some point you need your tools to be intuitive enough that you don't need to read an entire manual in order to do your work.

I cannot speak on behalf of the article author, but as someone who personally is an imbecile, the answer is: definitely!