ProgrammerHumor
futureIsNowOldEnv
Discussion
Don't let the past dictate your future. It was deprecated for a reason
That's just a warning!
If you are ever worried about backward compatibility, think of Python users, if they can live without it, so can your users. /s
No need for backward compatibility if no one is using it.
Semantic versioning to the rescue
You'll eventually pay the price for that someday with interest.
It happens with every technical decision meant to cut corners
That's the definition of tech debt
Yeah but that way of saying it is a bit more boring
This can work, but only if the decision is made with all related stakeholders. Get ready for some angry calls from managers if you as a dev decide to drop compatibility for a certain feature and sales or project management doesn't know anything about it.
I mean not really, but you do need to set an end of life
"Dear users, in this new release of our shitty library, the function replace_values() has been renamed to values_replace() for consistency reasons. Thanks you"
Backward compatibility? Bro I just npm install --ignore-the-past and vibe.
Look guys, glibc maintainers are posting on r/ProgrammerHumor
Is it that bad? Last time I heard was Torvalds ranting again. I haven't had problems with libc version but maybe Debian is that good or I'm that boring.
Torvalds is known for being very strict and mean and his rule of "we don't break the user API" but it's needed for a kernel and libc sits just above that
Yes it is, it broke steam, discord, etc. several times. The fact that you're on Debian might or might not have been a factor here cuz although they make 100% sure that nothing breaks before doing anything, I don't think they package proprietary stuff, so it's probably flatpaks that saved you (if you even use proprietary software because most times they're the only affected)
Yes Linus is very strict about "not breaking the userspace" and I wish glibc had the same rule cuz even tho is not the kernel, absolutely everything basically HAS TO link against it
Running programs built against older versions is fine. Building against older versions in a way which means your CI isn't stuck on the oldest distro & version you want to support is a pain, but that isn't really glibc's fault.
So many times had glib problems... then I discovered docker..(Debian with glib not musl)
OSses: Centos
glibc has great backwards (not forwards!) compatibility. They've only really broken it in the past to fix security issues.