How do big binary linux applications deal with it? ldd'ing my chrome, I see it using Ubuntu's /lib/x86_64-linux-gnu/libc.so.6 and even a lot of GTK/Gnome stuff is in there, with Gnome famously providing no backward compatibility guarantees at all.
They don't. They either just ship half a distro with the app (flatpak, etc) or make a couple builds for different popular distros and call it a day. Linux's userspace ABI compatibility is a joke. Who would want binary software right? Just build it from source!
You can make portable binaries if you statically link everything and use MUSL as your libc but this brings in a host of other problems. Dynamic linking is impossible to do completely portable too as the dynamic linker is a part of the distro and the executable bakes an absolute path to it!
This is FUD. Portable Linux distribution has been figured out as early as Loki and it's not all that different from Windows distribution: ship your dependenciens with your application (which is not even close to half a distro if actually care to think about what your dependencies are) instead of just assuming that whatever is on your dev machine will also be on other systems. It's really not that hard.
