3 years ago

Category: github

I’m normally a fan of the rigidity within the Go toolchain. The first real criticism I’ve had is with the way Go modules handle major versions.

Go modules, and the associated commands go mod and go get can be thought of as Go’s equivalents to NPM and Yarn.

For example: Go modules use git tags and semantic versioning to keep track of the versions of dependencies that are compatible with the module in question.

Each number is to be incremented according to the following standards: Go has decided that all versions beyond v0 and v1 are required to use the major version in the module path.