There is a big discussion between those that think a language without dependency management tooling does not make sense in modern times.
And those that think it should be abolished from the face of earth and replaced with git revisions and pure open source, regardless of industry needs.
Dependency management for Go is definitely on people's radar. https://github.com/tools/godep has been getting some traction.
Only works for source code packages, not binary dependencies.
There isn't a way to specific source code versions/tags in a portable way. Also makes the import paths dependent on your repositories.
> [go get] Only works for source code packages, not
> binary dependencies.
> There isn't a way to specific source code versions/tags
> in a portable way.
___
[0] http://peter.bourgon.org/go-in-production/#dependency-manage...
I am on the side for proper dependency management.
> It's one of Go's greatest strengths, actually.
Which will keep it outside the boring closed source enterprise commercial library tooling.
Does not seem very supportive of vendoring.
> I am on the side for proper dependency management.
"X? We don't need no stinkin' X".
Along the same lines, my mother used to always buy cars that were manual transmission and without power windows or locks, because they were features which made the car cost more, broke often, and were expensive to fix. The minor conveniences they afforded were not worth the costs.