News for hackers. Stuff that matters.
Re:Go’s Major Versioning Sucks – From a Fanboy by imtringued on Wednesday September 16, 2020 @08:17AM (#24491863)
>Project identity doesn't change if a project changes, it is not a new package.

It is a new package. From a practical perspective once you break backwards compatibility the new major version is its own independent thing. If you pretend its the same thing then you run into the situation where two libraries need v1 and v2 and therefore can't coexist. This is going to destroy your entire ecosystem. Replacing a few strings is nothing in comparison.

Re:Go’s Major Versioning Sucks – From a Fanboy by JamesSwift on Wednesday September 16, 2020 @09:45AM (#24492663)
I'm not sure which ecosystem you are referring to (golangs or the package itself) but it seems like there are plenty of existing ecosystems chugging along even though they do, in fact, treat the two versions as the same thing.

Not saying its right or wrong, but clearly it is not a death sentence.

Re:Go’s Major Versioning Sucks – From a Fanboy by noselasd on Wednesday September 16, 2020 @10:26AM (#24492999)
But it is cumbersome.

Linux distros have the same issue, rpm or .deb packages cannot have the same name but still support having 2 versions of a package/library installed.

If it's a shared library and they don't get the SONAME versioning right for incompatible backwards compabiliry, it's even more cumbersome, and incurs more work for everyone to consume that library.

Re:Go’s Major Versioning Sucks – From a Fanboy by sagichmal on Wednesday September 16, 2020 @12:03PM (#24493928)
It is a new package, from one perspective.

That perspective isn't appropriate to use outside of a narrow scope. In particular it's not appropriate to use at an ecosystem level, it's too surprising.