Linux

There is controversy in the nix world because nix flakes were (some say) merged without proper vetting first. OG nix diehards don't want to taint nix documentation with 'experimental' flakes. But probably the majority of nix users are all in on flakes. So you have documentation from the OG camp that doesn't include flakes, and you have innumerable unofficial guides for the flakes way. This on top of the quirkiness of nix the language and the multiple ways to do things. Unfortunate.

IMO nix-env was a mistake. It feels like an imperative package manager which may be comfortable to new users who are used to apt or similar. But really what you should be doing on nix is maintaining *.nix files which document/specify your system setup, and nixos-rebuild to update your system to that configuration. Similarly, nix channels are an imperative holdover, which can be done away with if you use flakes, which results in your current nixpkgs version being documented in a system level flake.lock file.

They have resolved this exact problem. There is an "experimental" cli tool that fixes a lot of your complaints about nix-env, nix-channel, etc. Itcs wrapped together with "flakes". This newer feature is a little different, and working with or without flakes segments the community AND the types of articles about nix, like this one.

As far as I know though, nixos related thing still have a bizarre set of commands, and even with flakes "nixos-rebuild switch --upgrade" is still how you switch configs.

And as far as installation goes, using nix-env -iA really is a bad practice. Thats installing something ad hoc like you would in any other package manager. That defeats the point of nixos, where your configuration file explicitly defines all the packages you need installed, and nothing else. Nix will remove any packages you didnt specify.

I do think it's important to emphasize the difference between installing software in user environments and system wide, which is why the tool is named nix-env. System packages must be installed via the nixos configuration file and a rebuild.

To me the biggest missing piece for new users is a tool to help manage your system configuration and reduce the frustration of having to constantly look up nix syntax or nixpkgs quirks. Maybe thinking of it as a nixos/nix IDE? Also a polished distribution built on nixos would be a good starting point (and easy to do, I didn't realize I could just copy someone else's configuration until well after I had my system working well enough)

The other thing that got me starting out is the need to garbage collect old packages. It's not strictly necessary if you have a large enough disk, but it took me several iterations of filling my root partition before I figured out how to properly clean up old generations.

Imho I wouldn't bother with nix-env or nix profile. It just creates a secondary list of packages that needs to be maintained and it's cumbersome to do so. There's nix-shell or nix shell if you need a package temporarily and there's your configuration.nix or flake for everything else.

Side note: nix profile at least has consistent commands: install/remove/upgrade

After trying out Nix as a package manager I realized I have a pretty different world view than the makers of Nix. I agree with the end goal but how they are trying achieve it is just alien to me. The nix command line is just downright user hostile.

I am personally hoping that someone else takes a stab at the Nix concept but have accepted Nix isn’t for me.

The errors are also pretty terrible, usually the thing that interests you is buried under a lot of text that makes troubleshooting a real pain.

I've read so many things that try to explain what flakes are, and for the life of me I still don't understand what they are or what they're for lol.

Here's an example of a tutorial that uses flakes and the new cli. You might glance through here to see how the syntax compares: https://zero-to-nix.com/start