> However, your code will be unusable by anyone who follows the normal Go way of coding.
Well, that's not really true given the major projects using tools like Godeps [1], so while that argument certainly sounds good, it doesn't actually seem to be a problem in practice.
Actually, CoreOS is using the version of godep that rewrites import paths, so that most developers can use "go get". The only time you need to use godep is when you're updating one of the vendored dependencies. That's actually the awesome thing about godep - it keeps your repo go-getable.
> the simplicity it presents to regular contributors and users used to go get make it worth the additional effort
Well, that's not really true given the major projects using tools like Godeps [1], so while that argument certainly sounds good, it doesn't actually seem to be a problem in practice.
[1] https://coreos.com/blog/godep-for-end-user-go-projects/