It sounds like Go has implemented package versioning /absolutely right/, this is how things should be. Two pain points stand out to me in the article though:

It sounds like Go has implemented package versioning /absolutely right/, this is how things should be. Two pain points stand out to me in the article though: > Users of packages aren’t alerted about new major versions > For the client to update, it’s not a simple path change in go.mod The tooling should definitely be enhanced to make these things easier to do - probably a flag for -u to update to major versions, and a builtin script to globally update all the imports when a major version has changed. Or maybe a way to specify a single 'default' major version in one place and then only needing to be explicit when using one that differs from that one. But this means you'd have files that could use different package versions if moved to a different project which could be unexpected.