Earlier quoted context omitted.
> Google and Apples's ... and Linux (well, Ubuntu specifically). I'm staring down the need to upgrade from Ubuntu LTS 20.04 to Ubuntu LTS 22.04 because some software I maintain now relies on GLIBC v2.32, which is an absolute bear to back-port. The party line is "So just upgrade," but there's no guarantee my hardware is compatible with Ubuntu LTS 22.04 because the vendor doesn't support that config and I'm not really…
> ...but there's no guarantee my hardware is compatible with Ubuntu LTS 22.04 because the vendor doesn't support that config... So it's your vendor who doesn't care about backwards compatibility - Linux does. Whatever hardware you have, once it was supported, it will stay this way until it is really ancient, and even then you will have special builds that will support it. That's the beauty of open source (or even sou…
(b) If Ubuntu (and I'm going to say "the Linux ecosystem in general") cared about backwards compatibility in the same sense Windows does, a minor-version bump to glibc wouldn't introduce API breakages that mean I can't build a codebase that's doing nothing new and special on my machine right now purely because a 31-subver bumped to a 32. They aren't doing anything new in the code; their JNI dependency just bumped up and so they bumped up the whole codebase's requirements.
That's fine, but it's not The Windows Way. The Linux Way doesn't think about compatibility issues like that in anything like the same way. It's a source-code-and-patch-it-yourself world. The approaches are completely alien to each other.