7 engineers on Hacker News describe using glibc first-hand: 0 endorse it, 5 regret it, 0 are mixed.
“ld.so's algorithm for symbol resolution was quadratic in the number of shared objects... there was a time before GRTE, when we didn't have a straightforward way to patch the glibc in prod.”
regret · production · ambrosio · 2025-12-29 · source ↗ · wrong label?“The termios code in glibc just didn't work. At all.”
regret · personal · xenophonf · 2025-11-09 · source ↗ · wrong label?“almost everybody who looks at memory usage in production will eventually discover glibc's memory fragmentation issues. This is how I learned about this topic.”
regret · production · nh2 · 2023-11-30 · source ↗ · wrong label?“glibc's hostility to static linkage (the whole NSS mess is farce) is why we moved to musl entirely”
regret · production · intelVISA · 2023-04-08 · source ↗ · wrong label?“Turns out GLIBC will read the resolv.conf once on startup and never again after (unless specifically invalidated).”
regret · production · stefan_ · 2022-09-18 · source ↗ · wrong label?“I was very active in thread on Linux over 20 years ago, working on glibc and whatnot.”
neutral · production · kazinator · 2025-10-20 · source ↗ · wrong label?“I just compiled it with the latest GCC and glibc, and carried on with my day”
neutral · personal · groovy2shoes · 2016-12-28 · source ↗ · wrong label?