[IshKebab]

Why? `go get` is an obvious default choice for package management. You don't have to make a choice.

There would be paralysis of choice if when you install Go you were forced to choose from that list, but you aren't.

[bobbyi_settv]

I don't see how something that doesn't allow pinning versions can be an obvious default choice for dependency management.

[spriggan3]

> Why? `go get` is an obvious default choice for package management.

I thought go get wasn't a package manager /s

[knucklesandwich]

You'd have a point if the default with Go was a good choice. In practice its not. It's a terrible choice that gives you no ability to use multiple versions of a package (across projects), control a project's dependency's versions, vendor a dependency or build from your system build directory on a case by case basis, etc.

The entire build chain with Go is probably one of the most frustratingly limited build tools I've ever used, which is probably why nearly every Go developer I've met has switched to using one of the third party options.