And when developers really need current versions of libraries/tools on an LTS distro, the solution is to recompile these tools by hand. And you end up with a Frankenstein system mixing an old base with multiple versions of monkeypatched, hand-compiled stuff.
-
-
Replying to @jedisct1
Each distro has some kind of (unofficial) "backport" repositories or similar where you can get the new stuff that you need. I very rarely need to make a custom build of anything non-Go or non-Rust, and all the Rust and Go stuff I have builds great with the latest stable releases.
1 reply 0 retweets 1 like -
Replying to @BRIAN_____
A lot of people and companies just don’t want to use backports.
1 reply 0 retweets 0 likes -
Replying to @jedisct1
Everybody wants something for nothing. What do people do prefer when they can't get something for nothing? My point is that maintaining backward compatibility is an anti-pattern that must have a significantly valuable motivation, which can/should be measured in money.
1 reply 0 retweets 8 likes
When I see people's backward compatibility hacks I can't help but think "that's bad code." OTOH, if they say "that paid for my kid's braces" then you can't argue with that.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.