News for hackers. Stuff that matters.
Re:Thoughts on “Dependency hell is NP-complete” by zzzcpan on Saturday December 17, 2016 @01:13PM (#13201677)
If you keep dependencies resolved at all times and operate on packages with hardcoded versions of dependencies, as Nix does, you can avoid that NP-problem.

Sadly, I remember people involved in Go packaging discussions being dismissive of Nix's ideas.

Re:Thoughts on “Dependency hell is NP-complete” by sagichmal on Saturday December 17, 2016 @01:25PM (#13201723)
You remember incorrectly. Nix, unfortunately, just isn't suitable for non-final dependency resolution, i.e. libraries. And that's an important part of the mandate for language packaging discussions.
Re:Thoughts on “Dependency hell is NP-complete” by zzzcpan on Saturday December 17, 2016 @01:40PM (#13201804)
Nix itself isn't suitable for many things, but the ideas those guys came up with are great and work well.