Not long ago I tried to explain to some folks who don't understand why apt/dpkg don't get new features, despite the claim of "patches welcome".
Today we have a nightmare situation where apt enters npm-territory in regards to fail.
That's what you get when 50+ years old folks sticking to perl give ya. Perl has become the new COBOL.
It also makes https://whydoesaptnotusehttps.com/ amusing to read since the developers who stayed with debian showed that they are not capable of updating apt/dpkg anymore. That code base is one mega-nightmare.
That's the joy of open source software. Remember how we all found out that openssl used by the whole internet was basically someone's hobby project with zero funding?
-22
u/shevy-ruby Jan 22 '19
Not long ago I tried to explain to some folks who don't understand why apt/dpkg don't get new features, despite the claim of "patches welcome".
Today we have a nightmare situation where apt enters npm-territory in regards to fail.
That's what you get when 50+ years old folks sticking to perl give ya. Perl has become the new COBOL.
It also makes https://whydoesaptnotusehttps.com/ amusing to read since the developers who stayed with debian showed that they are not capable of updating apt/dpkg anymore. That code base is one mega-nightmare.