4 ms·
> ...but at least it's generally easy to see what you did wrong and fix it. You're not actually "fixing" anything, you're just passing the ball of shit down th
by otabdeveloper4 2y ago
> ...but at least it's generally easy to see what you did wrong and fix it.
You're not actually "fixing" anything, you're just passing the ball of shit down the responsibility chain to the ops/infra team.
Which is fine if you work in a large corporation where this is a valid strategy.
Unfortunately though the software supply chain problem is a) very difficult and b) unavoidable.
Nix is the best (or maybe only) attempt to solve this problem with programmatic (vs organizational) tooling.
- kstenerud 2y agoI've got nothing against the fundamental concepts that Nix strives for. In fact, that's what triggered my 2 year journey with it. I just hate the implementation with a passion. The overall result is worse than before.
- otabdeveloper4 2y agoThere is no possible way to solve anything in this problem space without triggering developer PTSD. The implementation is not at fault. (See npm or the clusterfuck of Python packaging for proof.)