glibc

“It might be the best of the linux libraries but it's still not good.”

“It's basically the only library on linux that actually has a strong commitment to providing a stable ABI”

“one brain dead decision, to make it basically impossible to use different glibc versions on one instance”

“glibc has a bug where it doesn't support communicating a link-local scope ID in its name resolution subsystem.”

“glibc's AVX2 based memcpy functions have a non-negligible performance impact”

“c-libraries can actually do it better in many cases, especially for large copies”

“Glibc is terribly designed and it is the core component of almost any Linux userspace app today.”

“glibc is backwards compatible as long as a) your program is running on a newer version”

“glibc uses symbol versions that are forward but not backward compatible”

“gnu developed a system that worked, and then made it free to everyone to consult and use”

“In their defense the people working on glibc and gcc are pretty intelligent”

“Reading the linked bug report about executable stacks they fixed it? So they did the right thing.”

“I've had instances when the loader would refuse to load the executable because the installed glibc is too new for it.”

“glibc is quite compatible”

“which do support lots of architectures and more importantly make porting to new architectures or taking advantage of platform features pretty straightforward”

“These projects have made controversial design decisions which impact the entire ecosystem of Linux software.”

“glibc really doesn’t provide improvements to any of the kernel interfaces or really any comfort stuff for developers.”

“Each of these libraries is extremely popular and has a user base of billions of devices.”

“policies and principled stance are quite correct and overall "good for humanity"”

“glibc actually does a good job of using symbol versioning”

“those guys bend over backwards to provide strong API compatibilities”

“glibc has been investing heavily in ABI stability”

“Glibc has been a source of breakage for proprietary software ever since I started using Linux.”

“The glibc people are so serious about backward and forward compatibility”

“glibc is the only one who even has a compatibility story”

“debugged and hardened run-everywhere never-fails code”

“What I find amazing is why people continously claim glibc is the problem here.”

“Because I do not like certain decisions in the design of glibc, I am skeptical about their ability do define good standard APIs”

“Getting all of LLVM mesa linux cmake ninja glibc gcc binutils xorg KDE to work is more work than in 2005 or 2010.”

“It did help for programs built by those who know what they are doing.”

“But Glibc has pretty good ABI compatibility.”

“It seems impractical to expect every piece of software on your computer to be built against a specific version of a specific library”

“nothing ever lets you pick which versions to link to. You're going to get the latest ones and you better enjoy that”

“Versioned glibc symbols are part of the reason that binaries aren't portable across Linux distributions and time.”

“At least glibc uses versioned symbols.”

“It's really just an artifact of decisions from decades ago, and the cure is way worse than the disease.”

“The fact that multiple cancellation points are discreetly buried in the paths of these functions is an element of unfortunate design.”

“which has had ABI compatibility for decades”

“glibc and a small list of other base system libraries have strong backwards compatibility”

“GNU such as GCC and Glibc was also quite useful and successful”