| |||||||||||||
Re API (and ABI) design and maintenanceRe API (and ABI) design and maintenancePosted Nov 15, 2012 17:15 UTC (Thu) by nix (subscriber, #2304)In reply to: Re API (and ABI) design and maintenance by k3ninho Parent article: EPOLL_CTL_DISABLE, epoll, and API design
That's pointless. With memory sizes continuing to shoot up as they are, the memory overhead of maintaining old interfaces is minimal: and as long as the interfaces have no significant maintenance overhead, why not maintain them? I mean, Linux still supports uselib(), which is IIRC useless unless you're still using a.out shared libraries and libc4!
(Log in to post comments)
Re API (and ABI) design and maintenance Posted Nov 19, 2012 6:44 UTC (Mon) by k3ninho (subscriber, #50375) [Link]
This article itself supplies an example where an older interface design has caused internal plumbing designs to be less than the best. This will happen again, and will cause a kind-of scarring to the structure of the Linux Kernel. Wouldn't you like to be able to offer end-users of the Kernel a clean set of interfaces, easy to comprehend and unhindered by history's quirks?
K3n.
|
|||||||||||||