Badabinski

I’ve listened to most of the Culture series and I really liked it all. Look To Windward was especially good imo.

I love The Player of Games by Iain M. Banks. The audiobook is narrated by Peter Kenny and he does such a good job with it.

AFAIK, LFP thermal runaway can’t start fires. NMC or other lithium chemistries can and they scare me, but LFPs are pretty damn safe. That being said, I’m still stoked for sodium chemistries to be developed. If the round trip efficiency issues can be solved, then I think it’ll be a great solution for residential power storage.

I made the mistake of buying a Samsung washer/dryer set in 2017. The washer actually still works and the seal has held up well, but the dryer drum jumped its tracks within the first year, and both have been plagued with gremlins.

Fuck Samsung appliances and honestly most things Samsung sells.

26 years later and it’s still a fucking banger of an article: https://theonion.com/new-e-toilet-to-revolutionize-online-shitting-1819565332/

I wouldn’t necessarily say that. I used to shoot competitively (service rifle across-the-course), and we’d shoot 200 yards off-hand. We don’t know if the shooter was prone, sitting/kneeling, or standing. If they were standing (because they wanted to beat a quick retreat) then it was a hell of a shot. Honestly, even if they were prone it’s not bad. Given the nature of the shooting, it appears that the shooter didn’t want collateral damage. There were a LOT of people there, and that pressure would make any shot harder.

Here’s a link to the CVE itself, which has useful details: https://nvd.nist.gov/vuln/detail/CVE-2025-38352

I’m not using it because it would be extremely inconvenient for me, but I think that the English language deserves to have the thorn returned to it.

Y’all lol.

Yep, my org had a Falcon sensor outage take out tens of thousands of Linux servers. Fuck Crowdstrike. Also, fuck Windows and fuck Microsoft.

I’ve been on a Lethal Company kick for a few months. I’ve been getting super involved in the “high quota” scene, where people try to get the highest quota possible. It involves a lot of crazy tech and good team work, and I’m really enjoying it.

Yep, taking some care early on can pay dividends down the road. The data structures you choose really matter, and YAGNI can stop you from going overboard with indirection and other shit. Premature optimization is bad, but there’s nothing wrong with writing performant software as long as it’s still comprehensible and extensible.

Where would be manually modifying modules.dep and map files on this, I wonder?

The Blade Itself by Joe Abercrombie and the entire First Law series. The books are narrated by the wonderful Steven Pacey and they’re just so good. Pacey does an excellent job of conveying each character’s personality, and the way he narrates fight scenes are so good.

backscratcher/10

it was a form from Google soliciting feedback on the thing.

Lovely, thank you for this. I’ve left my feedback, and I hope many, many other people do as well.

It also lacks any form of dependency management AFAICT. I don’t think there’s any way to say you depend on another service. I’m guessing you can probably order things lexically? But that’s, uh, shitty and bad.

I wrote and maintained a lot of sysvinit scripts and I fucking hated them. I wrote Upstart scripts and I fucking hated them. I wrote OpenRC scripts and I fucking hated them. Any init system that relies on one of the worst languages in common use nowadays can fuck right off. Systemd units are well documented, consistent, and reliable.

From my 30 seconds of looking, I actually like nitro a bit more than OpenRC or Upstart. It does seem like it’d struggle with daemons the way sysvinit scripts used to. Like, you have to write a process supervisor to track when your daemonized process dies so that it can then die and tell nitro (which is, ofc, a process supervisor), and it looks like the logging might be trickier in that case too. I fucking hate services that background themselves, but they do exist and systemd does a great job at handling those. It also doesn’t do any form of dependency management AFAICT, which is a more serious flaw.

Nitro seems like a good option for some use cases (although I cannot conceive why you’d want to run a service manager in a container when docker and k8s have robust service management built into them), but it’s never touching the disk on any of the tens of thousands of boxes I help administrate. systemd is just too good.

Just journalctl | grep and you’re good to go. The binary log files contain a lot of metadata per message that makes it easy to do more advanced filtering without breaking existing log file parsers.