Not much software directly targets syscalls. Even just linking to libc (musl/glibc) exposes you to the churn of userspace linux.
Games depend on the entire stack (audio, HID, VR, Vulkan, desktop compositor choice, etc.) so are the most vulnerable to any minor change. And game developers, rightly so, have better things to do than to recompile if not re-port their game because Linux has decided that Pulseaudio is out, or X11 has been replaced with Wayland.
So yes, in practice, there are only two stable APIs/ABIs on Linux: the syscalls, and Proton.
"Even just linking to libc (musl/glibc) exposes you to the churn of userspace linux" Sure, but this is why sometimes people pack libc/libm into docker and had it running w/o problems - because for any decent kernel syscalls are stable ABI.
It’s a tongue in cheek comment, but the author does say:
> Personally I share Linus’ opinion (link to YouTube) that changing ABI is okay as long as no one has noticed, but once it gets noticed - then it’s a regression. Once it’s a thing people depend on, it becomes a feature.
No public write ups. What information would you want to see? I think there's two categories: infra ops info, and then product insights and "gotchas"/unintuitive but valid results.
reply