Hacker News Reader

Comment by beepbooptheory | Hacker News Reader

Kind of an interesting thing here where if this is how you view it, it kind shows in itself why you don't actually need it.

Like what is ultimately the difference here for you vs a non-nix user who, as author says, is just dealing with some big ambiguous pile of state? It kind of takes away any upside to using nix, and probably just creates more friction for your AI than just running ubuntu/apt stuff.

The idea is you can keep configuration "in your head" such that you can reason and iterate and fully know what your system is like at any moment. If you actually don't care about that, you aren't getting anything out of it!

View on HN

The upside of Nix config is that it's the state of my system in a declarative config file.

I have these packages installed and these firewall settings and these users with these permissions and this folder served over Samba and these hotkeys that do these things and these Obsidian vaults synced over SyncThing and these devices in my SyncThing network and Neovim installed with these plugins and ...

This is difference between me and a non-nix user, not whether we can rattle off the exact state of our live system from memory.

The non-nix user has to query live system state, if such query tools even exist for their question, and I get to read a config file. And I get to maintain my system config in git, and I get to deploy my config on all of my machines.

But if you are not reading or comprehending the config file, why does it make any difference? You ask AI to purge ffmpeg from your system, it will probably know more about doing that with apt than with nix, right? And if the input on your end is "remove ffmpeg from my system" or whatever either way, what's the need for nix? You will be much happier just editing /etc files and such in the standard way, rather than hoping your AI knows the (sometimes sadly inconsistent) way nixos handles the particular module/service/whatever you are dealing with.

For me, the difference is that there is no way in hell that I want to give an AI assistant full access to configure my system live. With a declarative config, the only access it needs is to an isolated git repo.

But if the declaritive file is not read/understood, what is the difference? At some point, you're gonna run sudo nixos-rebuild, and that is the whole system on the line.

> But if the declaritive file is not read/understood, what is the difference?

Well the main difference is precisely that I have a clear opportunity to read and understand the declarative file.

But even if something were to sneak in there, rolling back is now trivial.

This whole thing has been about explicitly using LLM instead of learning nix. So sure, definitely agree with about the niceness of using nix in general if that is all you are saying, but also not sure what you are trying to argue for anymore.

My point is that nix is a big enabler for me to use AI to configure my system, because it provides a safer environment in which to do so.

Very cool!

Reply on news.ycombinator.com