Earlier quoted context omitted.
> knowing that if I build an app and it probably won’t work in 5 years Would you say MacOS, Android, and iPhone are also hobbyist toys then? And by the way, if you statically compile your app for Linux it will basically work forever. Linus's mantra: We Do Not Break Userspace. These are userland problems and can all be avoided with a linker flag if it's a priority for you.
A statically compiled app that used Xorg won’t run on many Linux distributions at the moment. A statically compiled app that used Jack for audio might have problems running on PipeWire. A statically compiled app from 2012 that used PolicyKit for authorization might not work today when asking for sudo. Everyone’s moved on to polkit. The meme is wrong, don’t regurgitate nonsense. I can guarantee you my Windows app comp…
Not a single major distribution doesn't ship Xwayland by default. The entire gaming community relies on X11 continuing to work, just like they rely on x86 libraries to stick around.
> A statically compiled app that used Jack for audio might have problems running on PipeWire.
A statically compiled app that uses Jack for audio might have problems running on Pulseaudio/ALSA/OSS. Jack's never a thing that's generally available, so claiming it's a backwards compatibility issue is nonsense. If your application requires Jack, then you need to ship it.
Note that you'll also have issues on Windows and Mac because Jack - unsurprisingly - is not installed by default on those platforms either.
> A statically compiled app from 2012 that used PolicyKit for authorization might not work today when asking for sudo. Everyone’s moved on to polkit.
If you used policykit correctly you should have either used the dbus protocol, or the command line utilities. These are the APIs for userspace and they haven't changed since 2012.