pmarreck
3 days ago
There is likely a mass of devs that is probably, hmmm, 10x the number of Nix devs from over a year ago, who know exactly what Nix offers and why it is cool, but couldn't be bothered to master it until AI came along and basically "solved the problem".
So I'd expect AI to rapidly accelerate Nix adoption. Hopefully, because it is amazing.
0x457
3 days ago
Yeah, even you understand nix and make packages it was still a PITA to use sometimes. If something isn't in nixpkgs or you need a different version, it might be as easy as writting 20 lines of nix, or 2000.
Now you can just send this to agent "port dis <repo link>" and 20 minutes later you get a working package, or 20 working packages what were required for that package to work.
Fixing stuff also easy, just today for some reason my machine wouldn't wake up monitors after sleeping them, a few minutes later claude fixed my configuration. Making QuickShell things with it also easy. For years I've avoide all GUIs for networkmanager and bluetooth on linux because they all looked awful and unusable, now QuickShell things made just for me, exactly the way I wanted.
POiNTx
3 days ago
I've been using nix before you could use AI to write ok code with it and it was a struggle knowing how to configure nix sometimes. Especially when dealing with less popular software which happens from time to time. Still stuck to it as I've felt that once it was working it was pretty amazing. But using Claude with nix is super cool. It's really good and I don't care much about the quality of my nix config at this point, it's just for me and I just want my computer to do what I want it to do and Claude can figure it out most of the time.
unshavedyak
3 days ago
Heck i used Claude when it sucked just to ask it questions. It was wrong on 50% of the questions back then but it still was easier than randomly searching for the solutions. Claude helped unblock me when i got stuck on obtuse nix errors, foreign compilation issues, etc.
These days it's magical, but it was even a huge boon when it was barely functional. Nix just had a way of leaving me super confused and stranded.
skydhash
3 days ago
I tried using various configurations tools and to this day, unless it’s needed for a project, my strategy is “don’t bother”. When I use a program for a while, I backup the config somewhere and perhaps write a few notes, but my daily setup vary enough and last enough that I wouldn’t replicate it.
My mac setup hasn’t been replaced since 2021 or something, and it was copied from my old mac. I have a dotfiles git repo, which I drag around and have multiple branches for my daily driver. For temp setup, I just copy files and edit.
pmarreck
12 hours ago
most of us are not interested in doing extra unnecessary manual work to maintain these things or synchronize them across different computers or resurrect them after a certain amount of time not touching them
but you go with your time wasting self
jeremyjh
3 days ago
I think that ratio is possible, and certainly I’m counted among those numbers. However, it is not so much the case that I longed to use Nix and agents made it more feasible. What happened is that I wanted an agent to manage my machine’s configuration without giving it much access.
It’s not the only thing that agents have changed for me - I also went back to using neovim and tmux; partly because of how I use remote development servers but also because now I can get my setup working perfectly for me without a lot of hassle.
Open source and code managing all the things has always been a great idea but now it feels crazy to do anything else.
nine_k
3 days ago
Nix is amazing in many ways, but its discoverability and transparency are sometimes very poor. Its module system is anything but lean and straightforward.
I say this as a daily user of Nix.
mamcx
3 days ago
Is mainly the language. Is not just weird like APL , that insanely make sense. is weird.
nine_k
3 days ago
I don't find Nix the language particularly weird. But pick an arbitrary .nix file, see a bunch of stuff passed to the derivation, and try to find out whence it comes, and what types / attributes are expected there. The only definitely working solution I know is a full-text search over the file tree.
Now compare it even to Haskell, to say nothing about e.g. Typescript.
mamcx
2 days ago
That... is all on the language. In fact the main trouble now that you spelled out is the major blow against nix: is terrible at modularity!
a96
2 days ago
https://guix.gnu.org/ might fix the language by replacing it with a real one.
nine_k
a day ago
Guix is a nice idea. But the few last times I read about it, users uniformly noted that it's soooo slow in man cases. Nix can be slow, but most of the time is very fast, it just has to check a lot of files.
pmarreck
12 hours ago
The problem is that an immutable build architecture really requires a functional language to be aligned with it
jeremyjh
3 days ago
I don’t find it weird compared to other functional languages.
Shish2k
3 days ago
That's not the compliment that you think it is...
(I say this as somebody who deeply loves the concepts in most functional languages, and loves the concepts in nix, but recognises that the developer-experience of both is about as pleasant as reading somebody else's code-golfed perl)
jeremyjh
2 days ago
It isn’t a compliment, just a fact. Of course it all depends on what you are familiar with, but that is a fact about you, not Nix.
The concepts in functional languages are not fully realized in any multi-paradigm languages. So you can admire all you want, but don’t knock it until you’ve actually tried it.
pavo-etc
3 days ago
This is exactly me and I've fallen in love with nix
pmarreck
3 days ago
And I understand because it took me TEN YEARS to come around.
I worked with a very forward-thinking functional programmer around 2012 and even back then she was raving about it. And of course, people thought she was a raving lunatic.
I give her credit to this day. It took me having one too many problems caused by NOT using Nix, to cause me to finally dive in.
And there's no going back. Which is what happens with the best technologies.
cedws
3 days ago
Me too. I’ve known about Nix for a long time but resisted the idea of learning a new language just to manage my system. In retrospect, it would have been worth it, but now I don’t have to.
troupo
3 days ago
I find this take baffling.
"We have this system that is so amazing that... it requires a paid subscription to an LLM provider or a $5000 GPU for most people to understand and configure".
When instead Nix could've focused on releasing flakes 10 years ago with probably the same effect. And fix issues like this: https://news.ycombinator.com/item?id=50040083
rgoulter
3 days ago
It's not so strange.
Pre-LLM: Nix is "high effort, moderate reward". The cost is: you have to learn a tool which does things apparently completely different to how other tools do things.. you have to put up with a lot of friction, pay all the pain upfront, and the benefit is that may be later it's easier to get the package again.
It's just not a practical trade-off for most developers.
With LLMs, the cost-benefit trade-off changes.
You can use this cloud provider's LLM to get you a good result. You get the benefits, and the cost is 'just' "ask the LLM to do it".
Similarly: it's easier to assess whether produced code does the right thing, than to come up with that code from scratch.
Without LLMs? The inaccessibility also comes from being a niche tool. Not many use it, so not many software projects accommodate it or consider it, and you might have to come up with workarounds yourself.
troupo
2 days ago
This doesn't really do anything to dissuade me from my point of view. So it was a complex system with an extremely high barrier of entry that even nix proponents admitted.
It remains so, only now you want people to blindly trust LLM output for this system.
rgoulter
2 days ago
Some tools are good even though they have a high barrier to entry.
That people use resources to help them use tools they don't understand too well is hardly new. e.g. Classically you might copy-paste from StackOverflow after finding an error, or some people watch YouTube videos about it.
I'd say LLMs make it easier to get to the point where you can understand it, though. So it's an accessibility increase.
> It remains so, only now you want people to blindly trust LLM output for this system.
This isn't related to Nix, though. You could ask an LLM to create the most mainstream Python code ever and blindly trusting it would make as much sense.
For system management, Nix has the advantage of being declarative. e.g. For NixOS you get to read the code and review what it's doing.
charlieflowers
a day ago
Is the high barrier to entry essential though? Is there something about the nix domain that would mean any solution would have as high a barrier to entry? Or is it something they could have simplified greatly, and just never did? (Asking as an outsider, I've always been curious about this).
pmarreck
12 hours ago
I went into Nix thinking I would understand the whole thing and then distill a very simplified version, but as it turns out, a significant amount of the complexity is basically required for it to work like it’s supposed to, given how builds and runtimes and dependencies across various languages work, which is unfortunate
rgoulter
a day ago
Some parts could be smoother.
Here's a rough sketch: the Nix expression language is really configuration oriented; it's a "JSON + functions" kind of language. You write Nix to describe how a package is built; the ideal case being "./configure && make && make install" as such. The resulting packages are put in a Nix store. (Almost) every dependency is put in the Nix store; so your program links against libraries in the Nix store, or runs other sources from the Nix store.
- Nix is "just" declarations of those instructions which output into directories and everything gets symlinked. But, it can take time to build an intuition for how to do things.
- There's some fundamental friction where most Linux systems assume shared libraries are available globally in a typical place on Linux. -- e.g. Python's "wheels" come with precompiled dependencies which assume shared libraries are available in a global place. Nix doesn't provide that.
- "Why not just provide globals?" For one, by having everything not be global, you can have multiple versions available at the same time.
- Since Nix is quite 'strict' by default about everything coming from the Nix store, it practically means 'paying' for all the difficulties up front. (There's a trade-off where you could write packages in a less strict manner; this is great for iterating, but bad for maintainability).
- Since Nix is strict about symlinking all dependencies, often if upstream software does things in a "quick and dirty manner" (e.g. hardcodes "/bin/bash", hardcodes paths for binaries to run, etc.) then it can be difficult to describe how to package that software with Nix. -- Fundamentally, you're taking something which works loosely, and bringing it into a stricter system.
- Upthread the comment mentions "flakes". Flakes provide both dependency management (i.e. being able to declare other Nix codebases you'll use), as well as a standard entrypoint into a Nix codebase. -- Without flakes, the UX is a bit cumbersome..
- The majority of packages which people use come from "Nixpkgs" package repository. This has a lot of organic complexity to it, coming from multiple contributors, with competing ideas for achieving results.
- With Nix being a "json + functions" language.. not sure I'm articulating this right, but it means that practically a large codebase is built as a single 'expression' (i.e. soft boundaries between bits of code).. and the tooling for troubleshooting problems is ... not very good.
- The Nix expression language is functional and lazy. This can be rough for people who don't have this background.
- Since Nix adds a layer of abstraction, it means you might need to have both a broad and a deep understanding to get something working (e.g. understanding how to drive Python or Linux in non-conventional ways). -- A kind of "do everything properly" which more conventional systems don't require.
So ... some aspects could be easier. But I think there's a fundamental friction to it.
ngruhn
2 days ago
Flakes are not less confusing to me. Why do you have to git stage a flake.nix for it to apply? I ran into that footgun so many times.
pmarreck
12 hours ago
there is a legitimate reason why this is the case; it is probably instructive to have you look it up or ask an LLM
jeltz
3 days ago
Yes, this just confirms nämy view that Nix, as it is right now, is bad.
clivedup
3 days ago
And yet, it matches reality.
Flake stabilisation probably hasn't gotten any easier/more likely by LLMs, but it does make it quicker for people to pickup technology.
Technology sometimes has that odd effect. (And it will apply to different technologies in different contexts at different rates.)
p1necone
3 days ago
Yeah I tried to daily drive Nix at one point pre AI and the ergonomics were just not a good match for me - perhaps I should try it again.
californical
3 days ago
It really depends on the person, for me I have my own setup script that works on both Mac and Linux, installing all of my core software using whichever method is best for each system, I basically have a csv with columns of “program” “install command Linux” and “install command Mac” and it just works.
Then all of my dotfiles are backed up, with any important other config, in a big gig repo. And all of my documents/photos/etc live on a separate hard drive which gets backed up to the cloud.
All of that to say, with the right setup nix is mostly unnecessary, and honestly the benefit of not using it is that I can wipe my system anytime and restart it with just my usual important programs ready to go. Any mess made along the way gets purged automatically in every fresh install
pmarreck
3 days ago
I promise you that it will be worth it. Try again.
riedel
3 days ago
I love the combination.
I use devenv (yet another nix flake dev environments) and opencode.
It is quite a synergy : my nix usage profits from the agent and the agent profits from being able to install just anything.
I even vibecoded a plugin for personal use that runs all bash tool calls through devenv and uses the supplied nix lsp package:
riedel
3 days ago
Also being able to use wsl on my windows based work laptop added a lot to nixos affordance : https://nix-community.github.io/NixOS-WSL/install.html
Nihmie
3 days ago
Before AI, there was virtually no documentation, and there are so many ways to do any single thing that it makes it brutal to figure out what any given configuration was trying to do.
Is `nix` amazing though? Eh... if it were implemented better, it could be amazing. It's like python virtual environments or `pyproject.toml` for general software. It solves a real problem, but it does so by introducing a possibly even bigger problem.
pmarreck
3 days ago
No.
it's more like, it definitively solves a problem forever, like nothing else.
It's like when you have immutable data and it permanently solves a class of problems that can result from mutable data.
It's sort of like that.
pjmlp
3 days ago
I still cannot be bothered, even after reading this article.
ruiqingcn
3 days ago
[flagged]