2 ms·

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

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.

noselasd 6y ago
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.