> I don't understand why Go is so insistent that dependency management is something for the community to solve
The expectation that every new language should come with a dependency management ecosystem is a bit questionable. A lot of major languages' dependency management solutions were created by the community:
Java: Maven, Gradle
Python: PIP
Ruby: Gems
Node.js: NPM
Some of these have been adopted by the official language maintainers, but as far as I know, they originated in the community.
The problem is that Go implements a half-arsed way of dependency management (go get) and enforces things like GOPATH that clash with community created solutions.
The expectation that every new language should come with a dependency management ecosystem is a bit questionable. A lot of major languages' dependency management solutions were created by the community:
Java: Maven, Gradle
Python: PIP
Ruby: Gems
Node.js: NPM
Some of these have been adopted by the official language maintainers, but as far as I know, they originated in the community.