Fantastic summary. For anyone wondering how to get really really valuable in IT, this is a great write-up of why my top paid people are my top paid people.

As a Perl user who won’t shut up about it… Yeah. Yeah, that’s pretty fair.

Their out too git us!

This is great.

If I could make one change, there’s so many funnier languages that could have been Esperanto. I would have taken a shameless jab at F#, myself.

Yeah. I don’t mind snap at all for cases where a better package doesn’t exist.

What made me give up Ubuntu was how it railroaded me into snap versions of packages that work better, for me, as native .deb installs.

the thing people dislike about that is that you’re silently moved from an open system to a closed-source one.

Yeah. I didn’t realize I had fallen for it until I tried to automate a system rebuild, and discovered that a bunch of the snap back end seems to be closed and proprietary.

And a lot of it for no reason. Reasonable apt and flatpak alternates existed, but Canonical steered me to their closed repackaged versions.

FUCK IT, I BUILD FROM SOURCE CODE FROM SHADY GITHUB REPO_*

I feel seen.

Oh shit! So is mine!

Lol. It’s not the groundhog we should be watching, then?

They probably mean Open Container Initiative (OCI), the protocol shared by Podman and Docker.

Perl is the only language that looks just as incomprehensible before and aa rot13 transformation.

Lol. You’re not wrong.

I’m kinda jealous. I don’t miss maintaining production Perl code, but Perl was more fun to code in.

Lisp is the more logical choice.

Relevant XKCD. Python has replaced Perl, but things have otherwise changed quite little.

I think they forgot to pay themselves to use their product.

You are supposed to be tracking when they expire and then renew/replace them before they expire.

I’ve been told that, as well, but I’m not sure I see it… Seems like a lot of effort… (This is sarcasm. Or is it just too much honesty?)

Yeah. The idea of an automated C to Rust replacement of the Linux kernel is fascinating. As you say, there’s probably stuff in the Kernel that Rust’s compiler won’t allow.

I imagine it wouldn’t work at all, out of the box, but it might reduce the cost curve enough to make a dedicated team of very clever engineers able to cross the last mile, given time.

As cynical as I am of both Rust and AI generated code, it honestly feels like trying an automated conversion might be less of a long shot than expecting the existing Linux kernel developers to switch to Rust.

And I’m sure a few would kick in some thought cycles if a promising Kernel clone could be generated. These are certainly interesting times.

Lol. If Rust fans want a Rust kernel, no one is stopping them from building one.

Thank you for this. This is awesome.

shittingTurtle and victimTurtle are going into one of my professional slide decks as soon as I think I can get away with it.

I love it!

All great code started out as a shitty work-around that happened to work.

(I say this as someone with one of the more prestigious pedigrees in “not writing shit code”. All the theory I’ve learned helps, but at the end of the day the most important qualities of a line of code are: whether it got the job done, and whether is was obviously correct enough that the next developer left it alone.)