Hacker News Reader

Comment by miki123211 | Hacker News Reader

And to add to that, LLMs start with fresh context on each conversation, so they don't have the understanding of your system that human employees do. Nix lets you naturally encode that understanding in code (and in comments), making sure it never drifts from what the state of the system really is.

I never saw much point in Nix, but if you put it like that... now I want to try.

View on HN

Nix (& NixOS) are very much in the same "as code" as Terraform. -- You put in extra effort now, to save effort later.

This isn't traditionally 'practical'. It's quicker to just install the package, compared to writing a declaration that says to make the package available. (And for ops, Docker images won out in terms of practicality).

Nix also quite a steep learning curve.. I expect a beginner just wants to learn how to write a package in Nix, and not learn about 'derivations', 'instantiation', etc.

Interesting to see LLM coding agents adjust that trade-off: significantly reducing the cost to "write something in Nix", so the benefits become much cheaper.

It's true that the Nix language is quite difficult to learn. However, part of that is the poor documentation, and the weird situation where flakes are the de facto modern way of doing things, but are still treated as an "experimental" feature (which leads to further confusion when reading documentation based on the old way of doing things).

Luckily LLMs can help with this too. I asked ChatGPT to generate a course with just enough content to help an ordinary NixOS user configure their system, work with Nix code and flakes, and create/modify simple packages (which is rarely needed anyway). Just a few hours of that gave me a much stronger understanding than all the documentation / tutorials I had read before.

Reply on news.ycombinator.com