3 ms·
I don’t like Nix. It’s hard to use. It solves a problem that Docker already solved and Docker UX is much better. And it has a DSL that I think is unnecessary
by didip 4y ago
I don’t like Nix.
It’s hard to use. It solves a problem that Docker already solved and Docker UX is much better.
And it has a DSL that I think is unnecessary for the problem at hand.
- SuperSandro2000 4y agoIt really depends on your problem. If you need to patch docker images it often gets hairy.
- Smaug123 4y agoDocker definitely solves the problem imperfectly, though. Docker images simply don't compose, and this has caused me great pain: if you want image A plus image B, you can't do much better than a multi-stage build where you just magically know what you need to pull out of the first image. Nix, by contrast, composes perfectly, because packaging something for Nix involves precisely specifying what you need (as opposed to packaging something for Docker, which involves… splurging your package arbitrarily across a clean container).