Still valid:

[gisgeek@floss.social]

@Enalys The usual approach is using a containerized approach, BUT that changes exactly nothing, because even containers need upgrades, and at a certain point in time, you are fucked in any case. After 30 years, I have become quite choosy about computing choices based on the expected life cycle... Today, I tend to deprecate the use of frameworks and warn 'ex ante' about languages that are expected to fail by design.

[larsbrinkhoff@mastodon.sdf.org]

@Enalys 30 years ago comes out to around 1980, right?

[enalys@mastodon.zergy.net]

@larsbrinkhoff
Now it's 1996. 1980 was 46 years ago, but this meme is around since the 2010's.

[enalys@mastodon.zergy.net]

@PeterSommerlad
Yeah, this meme is around since the 2010's.

[larsbrinkhoff@mastodon.sdf.org]

@Enalys Are you sure? I was born in the 1970's but I couldn't possibly be older than 35.

[1div0@mastodon.social]

@Enalys SYN+ACK+FIN

[synlogic4242@social.vivaldi.net]

@Enalys also on bottom: Rustacean "rewrite" of the Linux GNU coreutils. except more like a dumpster on fire

[kroc@oldbytes.space]

@Enalys @PeterSommerlad “30 months”, oh sweet 2010s summer child. They aren’t even near to The Event yet, they’re going to think 2016 is as bad as it can possibly be

[leobistmans@mastodon.online]

@gisgeek @Enalys I run the same 25 years old perl code at work ...

[gisgeek@floss.social]

@LeoBistmans @Enalys
That's the reason why I still use #Perl intensively as explained here:

SM-Tools, Copernicus, FOSS and the reasons of inevitable choices and drifts — frankie-tales

(lovergine.com)

[brnrd@bsd.network]

@Enalys
We could update this with
"Unix program written 30 yr ago"
"Unix program rewritten in Rust in 1 yr"

[a@pdx.social]

@Enalys @me_ Clearly we should rewrite it in rust.

[elithebearded@fed.qaz.red]

@gisgeek @Enalys

Python, Rust, Go, JS, and what else?

[gisgeek@floss.social]

@elithebearded @Enalys Some languages are more prone to breakage on upgrade than others, and lately, the FAFO attitude has become popular.

[bart@floss.social]

@Enalys In all fairness, 30 months is 100 Javascript years.

[albi@furry.engineer]

@Enalys Not to be a doomer or an AI buttlicker, but I do think with the new AI tools we might start seeing some of the old holes still present in our software.