4 ms·
To misquote the street fighter movie: OpenBSD to Linux: "For you the day you changed your ABI was the most important day in your life, but for me? It was Tuesd
by somat 1y ago
To misquote the street fighter movie: OpenBSD to Linux:
"For you the day you changed your ABI was the most important day in your life, but for me? It was Tuesday"
I enjoy the dichotomy between how bad the Linux project is at changing their ABI and how good OpenBSD is at the same task.
Where for the most part Linux just decides to live with the bad ABI forever. and if they do decide it actually needs to be changed it is a multi year drama with much crying and missteps.
I mean sure, linux has additional considerations that make breaking the ABI very scary for them. the big one is the corpus of closed source software, but being a orders of magnitude bigger project and their overall looser integration does not help any.
- viraptor 1y agoThis has nothing to do with Linux-the-project. An equivalent change would be in glibc / musl / ...
- ioasuncvinvaer 1y agoI think the difference is just the amount of people using the technology.
- MrStonedOne 1y ago[dead]
- badsectoracula 1y ago> bad the Linux project is at changing their ABI and how good OpenBSD is at the same task From my perspective as a user who wants to have his programs keep working whenever the OS updates and as a programmer who does not want to waste their time playing nanny with broken dependency upgrades for previously working code (working in the sense that it did what it was supposed to do), the Linux project is actually doing the thing the right way and OpenBSD the bad way. It is basically the #1 reason i never considered using OpenBSD. Linux' stance on not breaking backwards compatibility is exactly what i want from an OS. Now if only the userspace libraries weren't so happy to break things too...