The Grumpy Editor's guide to surviving the systemd debate
The Grumpy Editor's guide to surviving the systemd debate
Posted Nov 18, 2014 0:36 UTC (Tue) by nix (subscriber, #2304)In reply to: The Grumpy Editor's guide to surviving the systemd debate by tao
Parent article: The Grumpy Editor's guide to surviving the systemd debate
Why is libc shipped as one unit, instead of libc-str, libc-float, libc-stdio, ...? Because it's all developed as one single unit and because most of its users will be needing a lot of the components anyway. Andm being a system library, most systems will have use for all of these components.Really, really no. It's shipped as one thing because it implements one set of standards (the POSIX library specification, roughly, and its ancestors and relations), because it always was one thing, and because it has insanely strict backward-compatibility constraints so cannot ever stop being one thing (at best you can replace libraries with stubs and migrate their contents into libc or replace libc implementations with forwarders and migrate their contents out, and even that can be and has been problematic).
Unless, that is, you really think people use strfry() or memfrob() a lot.