And C# now can be taken off the donkey and mounted on a penguin and works rather well.

It's a heavy duty hilt that's easily detachable by a small recessed switch labeled “any”.

(It does its job very well as long as you don't opt out of using it)

because it makes it (type)safe to use..!

Also C# (or should I say the .net framework) is now cross platform, which wasn't really the case when I first saw this meme.

This joke made sense when instead of .net you could only use Mono with C# on other platforms, which wasn't very good at the time.

And Python's migration to 3.x is more or less complete. Took a while (15 years since 3.0), but it's to the point where migration is not a common topic of conversation.

Thank you! The original source of truth! 💎 As IT people, this is part of our culture and should be transmitted. 🤣

C is reliable in the sense that your C program reliably has memory leaks and security holes.

As does C#. The Windows-specific parts are not the parts most developers will use these days.

Agree. That one didn't age well...

The M1 Garand is known for having a problem during reloading where you have to stick your thumb in a slot that's about to shut very hard. There are techniques to avoid getting pinched, but "Garand thumb" is a well-known phrase among vintage rifle enthusiasts.

This fits C very well.

And does anything require Python v2 anymore? I work almost exclusively in Python and haven't run into that in many years.

But it can just blow up in your face

[flips safety off[

Powershell suffers from the typical Microsoft problem: Ignore for decades, and then go completely over the top with it.

For that matter, there are still folks out there coding, professionally, in FORTRAN.

Thing is, back then, we didn't know any better. Software was a commodity, and both the people who wrote it and the people who bought it had grown up in a time before the internet, before SaaS; people whose parents who, if they made things, made widgets.

Back then, you could write a piece of software, and it was done. Then you sold it, and moved on. If the old software had bugs, if they weren't catastrophic enough to cause a lawsuit, buyers learned to live with them. It was too bad; you already shipped the tapes. And few companies employed their own software developers unless they were software development companies. Man pages have a BUGS section, and that's because there's no intention to ever fix those bugs, because that software is done.

Software today is never finished. Our first reaction if we see a project with no recent releases is that it's abandoned, or dead, and certainly that it's worse than a project with recent commits to the repo. Github is a huge culprit in reinforcing this mentality, but mobile app platforms (stores and OSes) are terrible about this, too. Google constantly changes the Play store in ways that force developers to tweak their apps lest they become incompatible, booted, or get flagged as being "old" a.k.a. "inferior."

Yet, still, there's so much software out there that's complete. An institution may hire a developer to come in and make a change, but it's usually a contract one-off; it's more like taking your car in to have the starter replaced. Those systems are going to continue keeping "dead" programming languages (commercially) alive for years to come.

Cobol as a shield would also fit with it inexplicably still be in popular use long after anyone expected!

Not even Debian comes with Python 2 these days.

It was only removed 9 months ago

Assembly is a scrapheap with every sort of technology imaginable but it's all broken. Could be an iron man suit, or you could just grab a length of rebar.

back in my day that took 3 hours to download