Does Nix do one layer per dependency? Does it run into >=128 layers issues?
replyIn Spack [1] we do one layer per package; it's appealing, but I never checked if besides the layer limit it's actually bad for performance when doing filesystem operations.
Yes but then you're committed to using Nix which doesn't work so well the moment you need some software not packaged by Nix.
replyWant to throw a requirements.txt in there? No no, why would you even ask that? Meanwhile docker says yeah sure just run pip install, why should I care?
LLMs are getting very good at packaging software using Nix.
replyThen you're committing to maintaining a package for that software.
replyLike all LLM boosters, you've ignored the fact that the largest time sink in many kinds of software is not initial development, but perpetual maintenance.
It's not materially any different from maintaining lines in a Dockerfile.
replyThis. I wouldn't have touched Nix when you needed someone who was really good at Nix to keep it working, but agents make it viable to use in a number of place.
replyPackaging for nix is exceptionally easy once you learn it. And once something is packaged, it's solved for all, it's not going to randomly break.
replyIf you care about getting it to work with minimal effort right now more thar about it being sustainable later, then sure.
I use software from pretty much every language with Nix. And I package it myself too when needed. Including Python often :)
replyNix doesn't make sense if all you're going to use it for is building Docker images. It only makes sense if you're all in in the first place. Then Docker images are free.
replyEspecially if you use nix2container to take control over the layer construction and caching.
reply