I still maintain stabilizing async rust in its current form was a massive mistake and we're worse off for it.
Jason King
- 31 Followers
- 32 Following
- 164 Posts
illumos. Ex-Joyeur. I write C, Rust (when I can), and other languages and enjoy building end-to-end systems.
Dany 
I felt that Microsoft Copilot, formerly known as Office, could use a mascot. So I asked Copilot to design something in the spirit of Clippy.
Let me introduce you to Sloppy, a cheerful slightly gooey assistant with glasses and a headset.
Found an issue where go binaries would have intermittent DNS errors while the rest of the system was fine. Turns out the go runtime will often use its own built in resolver. In this case, the go resolver couldn't deal with the responses while the system resolver has no problems.
This trend of reinventing things that work fine (this isn't unique to go), leading to potentially divergent views of the world on the same system is both obnoxious (I'm looking at you DNS over HTTP) and just leads to lower software quality. Stop it!
Phil Spectrum
Every time I have to deal with iSCSI, I'm feel like channeling Mrs. White at the end of Clue
Has anyone else (in C) wrapped an int type in a struct to avoid accidental mixing of ints with different semantic values?
Oh firmware, will you ever not stop being terrible?
Really annoying when industry groups produce _large_ PDF specifications without a table of contents that you can use to skip to sections. Or when they do, they, completely screw it up. Looking at you trustedcomputinggroup.
God 
Thou shalt accept, DEI didn't hold your career back -- you're just mid, bro.
Once you're used to ZFS boot environments and are used to things like pkg(1) née pkg(5) just working for decades without any major problems (and none that could't be fixed with a quick and easy rollback), it's a stark reminder how pampered you are when you have to deal with systems that are every bit as clunky and brittle as they were 30 years ago (I'm looking at you RedHat).