> Dependency management in Go is so incredibly bad it's hard to fathom. It used to be pretty terrible. Today it's at least as good as npm. > Did no one on the

> Dependency management in Go is so incredibly bad it's hard to fathom. It used to be pretty terrible. Today it's at least as good as npm. > Did no one on the early design team ever deal with depenencies? It was developed at Google and they have a giant monorepo, associated infrastructure, as well as company policies against multiple versions of dependencies. They also vendor external deps into this repo. So no, Google deals with dependencies a lot, but they do things very, very differently from almost everyone else.