ProgrammerHumor
futureIsNowOldEnv
Discussion
Don't let the past dictate your future. It was deprecated for a reason
That's just a warning!
People compiling without switching on "fatal warnings" deserve exactly what they get…
I prefer to get a cve to solve and then discover that reactor Kafka has been discontinued in the moment.
If you are ever worried about backward compatibility, think of Python users, if they can live without it, so can your users. /s
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
No need for backward compatibility if no one is using it.
Semantic versioning to the rescue
"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"
“Dear users, we have listened to your feedback and …”
Where's the problem?
You guys don't have something like Scalafix?
When you release some change like renaming some symbol you just release it together with a Scalfix rule and user code will be automatically rewritten during lib update.
(Of course this only works in typed static languages, where semantic info about the code is 100% reliable.)
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.
Yeah it depends who your customer is. If you are planning on hugely breaking the interface of a public SDK or API without having done several releases with marked deprecation, then think about how much you hated that the last time some OTHER bastard did it to YOU.
> Apple has entered the chat
Their complete ownership of the vertical development stack has allowed them to introduce changes with relative impunity. Or, to put it another way, their slogan at WWDC should either be “We Hate Developers” or “Yeah? What Are You Going to Do About It?”
Windows "we tried our darnest so with enough toggles, you can still run older stuffs from 90s" vs MacOS "if your apps are no longer compatible, you are the problem"
The day I no longer had to support IE8 was sofa king liberating
IE8, what’s that?
Is a thing lucky people will say someday.
IE8 was almost standards compliant.
Ever worked with IE6?
Backward compatibility? Bro I just npm install --ignore-the-past and vibe.
I mean not really, but you do need to set an end of life
Put a bounty on the feature and wait for someone to submit a pull request.
Lol
Thats called moving on from your past.
I once had a walmart contract.
We was well down to Internet Explorer 6 being down to like 15% of the market... the phase where you can start actually arguing the time & cost isn't worth it now
They had it in the contract you had to target IE6! I couldn't believe it but thats what it was!
I know its not that way now but if you worked during that time it was so common... plus their like tiny business cards
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
Still somehow better than Musl
Or is it?
Vsause music
It depends, musl is widely used eg. in containers
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.