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.

The only way to know if you are competent coder is for other coders to tell you. If none are telling you, your imposter syndrome isn’t.

Or, considering that they’re mostly introverts, if they look approvingly in the general direction of your shoes…

This is particularly interesting, since modern organizational theory tells us that Boeing’s primary customers would be much better off with a shift in power toward Boeing’s workers, away from it’s current leadership.

Purchasers of huge airplanes cannot afford to purchase airplanes built under leadership that cuts corners the way Boeing’s leadership lately has.

The striking workers may have an unusual ally here - in Boeing’s customer base, which notably includes the US Government and parts of it’s Armed Forces.

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.)

At this point I think there is no software dev topic that is somehow not devisive.

Now I want to try something:

“Boolean variables don’t suck.”

Wow. “peak shareholder value” is what I shall now call “multiple inheritance”, from now on.

Thanks. I hate it.

I consider myself a collector of programming anti-patterns, but I didn’t have this one yet.

I’ll bet people said the same thing when Intellisense started suggesting lines completions.

They did.

And when errors were highlighted in the code rather than console output.

Yep.

And when high-level languages started appearing.

And yes.

That said, if you believed my mentors, we were barelling towards a 2025 in which nothing running on software ever really worked reliably.

So they may have been grumpy, but they were also right, on that point.

Tell me about “Why do you think you wanted to run ELIXA on a Times/Sinclair 2968?”.

Ditto. I use Go for this kind of thing.