Russ Cox on Go dependency management
> Dep does not support using multiple major versions of a program in a single build. This alone is a complete showstopper. Go is meant for large-scale work, and in a large-scale program different parts will inevitably need different versions of some isolated dependency.<p>This seems to be a major sticking point but I'm having trouble understanding why.  I'm not familiar with any other package management system which supports simultaneous major versions in a single project.  If two things require different versions of a package, those seem like separate projects to me.  Is this to support dependencies which rely on the same package at different versions?  If so, why not just call it a version conflict and fail until it's resolved?