I don't think the annoying thing about it is the classpath-like thing (and even if it were, it's at least not as bad as that, not requiring a directory for each

I don't think the annoying thing about it is the classpath-like thing (and even if it were, it's at least not as bad as that, not requiring a directory for each path component), but the fact that everything is predicated on this assumption that I'm only working on one thing (or ecosystem of things). I don't want project A and project B to be forced to share dependency versions, but Go makes you go to some pretty bizarre lengths to avoid that. I'd rather have a directory for a project and have its dependencies inside that in pretty much any language/environment.