News for hackers. Stuff that matters.
Re:Dependency graphs of Go web frameworks by merb on Sunday September 04, 2016 @01:18PM (#12425483)
> but your tooling reliably makes it easy to get them, build them, and upgrade them, is that hell?

Dependencies are never free. If you have a bunch of dependencies and not have too much resources it's still hell. Managing dependencies is not hard because of the tooling. It's hard because a dependency upgrade could cause pain, or the current version is buggy but the fix inside the upgrade works, but there will be another bug and so on.

Re:Dependency graphs of Go web frameworks by steveklabnik on Sunday September 04, 2016 @01:50PM (#12425694)
Right, this is what I mean: different people mean different things by "dependency hell". Difficulty of upgrading is certainly a possible meaning, but it's not a unified term.
Re:Dependency graphs of Go web frameworks by merb on Sunday September 04, 2016 @03:02PM (#12426105)
actually people just trust too much other people. but since you don't know anything about other people you should not trust them and especially not trust their ability to create good code.
Re:Dependency graphs of Go web frameworks by karma_vaccum123 on Sunday September 04, 2016 @04:01PM (#12426423)
Wrong. You trust yourself too much. A vibrant, well-documented and tested framework will likely be better than your own one-off code

If you really believe what you say, why are you using Go (or Java, or Rust or whatever) at all? Someone else wrote it...