2 ms·
Wait did you just call Go versioning and dependency management "easy"??
by paulddraper 4y ago
Wait did you just call Go versioning and dependency management "easy"??
- 2h 4y agoI dont have trouble with it. Link to my code is in my bio, wheres yours? Unless you actually write Go code, I dont think you have a leg to stand on here.
- cure 4y agoCompared to the dumpster fire aka Python packaging, Go versioning is easy and predictable indeed.
- silverwind 4y agoUntil you hit the obscure rules around v2+ go modules.
- 2h 4y agoI 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 4y agoSemVer 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 4y agomy biggest project has 13 stars, so I think I can do what I want with it.
- paulddraper 4y agoFair
- jerf 4y agoAre you running on 5+ year old data now? I'm seriously asking, because I'm actually a bit mystified as to the people who think Go's dependency management is some sort of disaster nowadays. Just about the only question I've fielded every so often in the past several months have been people who found their way to an old tutorial based on the old system and them being confused about what happens, and a quick link to the current docs seems to resolve all their problems.