[0] https://github.com/coreutils/gnulib/blob/master/lib/parse-da...
If size is really a concern, we have supported building a single 'coreutils' binary since 2014, which will be more effective in saving disk space. It can be done with './configure --enable-single-binary'.
There is also the rest of the whole "gnulib" folder inside the coreutils repo. Yes, I know that Gnulib explicitly states in the docs that it's a source code library but it doesn't bother to explain why exactly it chose to be that instead of being a .so à la glibc (beyond some rather unrelated "but supply chain attacks!" segment in the docs — if I cared about that, I'd statically link the relevant parts of glibc as well, in fact, that would be a much higher priority).
Gnulib also doesn't make API stability guarantees like shared libraries do. If a distribution installs Gnulib as a shared (or even static) library, and then links programs to that instead of the vendored sources, they will likely end up with broken programs.
[1] https://www.gnu.org/software/gnulib/manual/gnulib.html#Libra...
Also, "Gnulib doesn't make API stability guarantees like shared libraries do" — a) do you mean ABI? b) why not? The gnulib seems like something that's perfectly suited to be a shared library, even more so than the glibc, since it's not a language runtime.
2/5
And the .so dependency hell is real. You try to build some older version of a certain language runtime, it complains that your libssl/libcrypt lacks the functions it needs (those functions were in 1.0.1f, but 1.0.1k dropped them because that's how semver works), and of course your distro doesn't have the older version of libcrypt packaged for it so you take the package from the previous version of your distro, and it complains that your libc is too new and segfaults. Well, you sure as hell ain't rolling your system's libc to an older version so you try to rebuild libcrypt from the source, but the build with default config/flags still doesn't satisfy this certain language runtime and oh my god why am I even wasting my time on this, "docker pull certain-language:ancient" it is. Yeah, sure, this image has essentially Ubuntu 14.04 inside of it but at this point IDGAF. Why can the same 6.16 kernel run the user space both from today and from ten years before it, but the userspace from today can't run the program from eight years ago?