After daily driving NixOS and the Nix pm for almost three years, it feels like it’ll be simplified by entities external to the project. It’s still in that academic phase (don’t do this/that) and needs software engineering asap.

That usually involves reducing boilerplate ruthlessly while generalizing/capturing fundamental uses cases (setting implicit best current practices). It’s reminiscent of lxc just before docker arrived for the masses.

btw this blog is served to you by NixOS :-)

I’m just now realizing that there might be a schism within the Nix/NixOS ecosystem/community on old versus new interfaces. If that’s remotely true, then somewhere, a great holy war is at play. Here’s an article summary of the old versus the new interface that I stumbled upon recently.

This blog is really really good for robust usage of Nix/NixOS. I stumble upon it every so often. Another excellent blog is “How to Learn Nix” which explores in excruciating detail the painful parts of nix and its documentation. Discovered that one recently.

What’s funny about the NixOS/GNU Guix design is that it tricks developers into writing their own system packages. That would never happen on other Linux distributions. I’m slowly favoring Guix though, since the new nix flake interface couples too tightly with git.