[cure]

Compared to the dumpster fire aka Python packaging, Go versioning is easy and predictable indeed.

[silverwind]

Until you hit the obscure rules around v2+ go modules.

[2h]

I have been coding in Go for years, even professionally sometimes, and I have never had to use "v2" in any of my code. granted my stuff is not popular, but its really just a way for popular repos to handle big changes. Once I got past v1.9.9, I just changed to v1.10.0.

[silverwind]

SemVer dictates a new major version on every breaking change, but it seems this concept is alien to many go developers and they just release breaking changes in patch releases, at the detriment of the ecosystem.

[2h]

my biggest project has 13 stars, so I think I can do what I want with it.

[paulddraper]

Fair