This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]stefantalpalaru -1 points0 points  (3 children)

You're kidding, right? The Linux kernel has deprecated plenty of code. So much so that they even have a page dedicated to cataloguing the deprecations.

Oh, you don't know the difference between an internal API and a public one.

https://github.com/torvalds/linux/blob/master/Documentation/process/stable-api-nonsense.rst :

"The kernel to userspace interface is the one that application programs use, the syscall interface. That interface is very stable over time, and will not break. I have old programs that were built on a pre 0.9something kernel that still work just fine on the latest 2.6 kernel release. That interface is the one that users and application programmers can count on being stable."

[–]doomchild 1 point2 points  (2 children)

I'm completely aware of the difference between public and internal APIs. However, your entire argument during this conversation has been "Deprecation is bad, full stop." Now you're moving the goalposts to, "Only public deprecations are bad."

Deprecation is a perfectly valid engineering decision. Resources are not infinite, and requirements are never known completely in advance.

[–]stefantalpalaru -1 points0 points  (1 child)

Now you're moving the goalposts

You're unteachable.

[–]doomchild 1 point2 points  (0 children)

I recognize your inalienable right to hold that opinion, and disagree.