If glibc updates its version number and EAC starts failing because it used too small a data type for that, does that mean glibc broke ABI compatibility and should be stuck on a lower version forever?
Closed source software that wants to hold back open source software can go pound sand. Gamers can run their games with older glibc in a chroot / container. I say this as someone who does exactly this for games.
In the Windows world the answer to that question was emphatically "Yes, you should contort yourself to make sure users can still actually USE their computer", to the point that the official version number of windows was "3.95" because some apps looked at only the minor version number and would have broken otherwise.
Other stuff like the game Shovel Knight and even an open source frame limiting library broke because of this change, there are probably more things but this has not reached the masses yet.
I dont think the change was inherently bad but just ham fisting it into the release without widely announcing that the ABI will change is a massive failure on the glibc teams end.
Closed source software that wants to hold back open source software can go pound sand. Gamers can run their games with older glibc in a chroot / container. I say this as someone who does exactly this for games.