syklemil

And even with a "please keep your feet on the floor" sign right next to them.

I mean, the fact that more than half-century-old COBOL continues to be maintained does speak to the fact that it is maintainable. That might also be part of what makes COBOL painful to the average developer: You're not only dealing with a language that first appeared in 1959, designed for machines that were very different than modern computers; you're also dealing with over a half century of legacy code, including all that means for Hyrum's law.

Unfortunately maintainable and pleasant to work with are rather distinct concepts.

I also find that calling systemd "SystemD" is a tell that someone is unfamiliar with or has a conspiratorial relationship to it. It's named "systemd", all lowercase (but I'm likely to capitalize it on sentence starts like a normal word). Using an ungrammatical uppercase D at the end of the word, that isn't even something the creators claim is correct, is … a choice.

(And it's a choice that reminds me of e.g. how rabid anti-cyclists in Norwegian can't even spell "cyclist" correctly, but instead consistently use "bicycleist".)

The part is constructed from two parts:

1. ls: list
2. usb: usb

It lists usb devices that your machine (/kernel) knows has been connected; they may not necessarily be usable.

E.g. I have some sound output device connected via USB to one machine. On most of my machines I've switched from pulseaudio to pipewire¹, and I figured I'd bring that machine closer to the others so there's less variance. Unfortunately the sound output device didn't want to work with pipewire. The problem manifested as no sound and pipewire not listing the device. lsusb helped me know that the machine at the very least recognized the device, but wasn't currently able to use it. (It did actually also show up as an error in dmesg -H, but reinstating pulseaudio let the device work again as normally. So now I just have to live with a situation where some machines use pipewire because ~bluetooth~ and others use pulseaudio because … usb?¹)

¹ There's a memory of ALSA vs OSS I didn't want to be reminded of

Eevee's heteroglot entry for COBOL is interesting, coming from … practically anything else.

There's also someone doing AOC in ABAP (basically SAP COBOL) who posts over in the AOC subreddit. I've looked at them and ... mhm, I know some of these words!

There are also a bunch of proposed 2025H1 goals. Depending on how things pan out, 2025H1 might have us see not only Rust 2024 edition, but also the new trait solver ready for general use, and new borrowchecker on nightly.

In addition to the other comment about the exit code, you might be interested in the exitcode crate, which offers up a BSD convention for those exit codes.

They are, essentially, just numbers on unixes and don't really have as much standardization as e.g. HTTP codes afaik. Various programs may have their own local conventions as to what an exit code means.