Why glibc is such a critical lib for other applications?
by fulalas from LinuxQuestions.org on (#5DA6Z)
I always wonder why when glibc gets updated so many applications stop working. Why so many applications rely on the specific version of glibc?
I'm a developer and I can't imagine creating a piece of software that will stop working when glibc gets updated. Also, correct me if I'm wrong, but on Windows the equivalent lib (msvcr.dll) doesn't break applications when it gets update -- that's why we can usually run really old applications on recent Windows, and vice-versa.
Is it really so hard to not break an API every time the project gets updated?
I'm a developer and I can't imagine creating a piece of software that will stop working when glibc gets updated. Also, correct me if I'm wrong, but on Windows the equivalent lib (msvcr.dll) doesn't break applications when it gets update -- that's why we can usually run really old applications on recent Windows, and vice-versa.
Is it really so hard to not break an API every time the project gets updated?