2 ms·
Whenever this comes up I feel it is worth pointing out that Linux's "Things break" approach is a problem exclusive to the userland tooling built up around the k
by AnIdiotOnTheNet 9y ago
Whenever this comes up I feel it is worth pointing out that Linux's "Things break" approach is a problem exclusive to the userland tooling built up around the kernel. Linus takes a very hardline stance against breaking kernel ABI compatibility (except for drivers), but pretty much every piece of software outside of that, including GLIBC, thinks it's totally ok to break things all the time.
It's really very sad that the Linux community never adopted Linus's view.
- jhall1468 9y agoBecause they are entirely different things. Breaking the kernel ABI doesn't just break a few packages for a popular language, it breaks the entire ecosystem. More importantly there's literally no reason to break compatibility in the kernel. There are perfectly valid reasons to break compatibility in programming languages. Apples and oranges comparison.
- jgalar 9y agoEven the kernel occasionally breaks interfaces. Case in point, FUTEX_FD was introduced in 2.6.0 and retired in 2.6.26 [1]. I don't think anyone working on glibc is intent on breaking user space. Sometimes it's just the most pragmatic solution. [1] http://man7.org/linux/man-pages/man2/futex.2.html http://man7.org/linux/man-pages/man2/futex.2.html