Want to wade into the snowy surf of the abyss? Have a sneer percolating in your system but not enough time/energy to make a whole post about it? Go forth and be mid: Welcome to the Stubsack, your first port of call for learning fresh Awful you’ll near-instantly regret.
Any awful.systems sub may be subsneered in this subthread, techtakes or no.
If your sneer seems higher quality than you thought, feel free to cut’n’paste it into its own post — there’s no quota for posting and the bar really isn’t that high.
The post Xitter web has spawned soo many “esoteric” right wing freaks, but there’s no appropriate sneer-space for them. I’m talking redscare-ish, reality challenged “culture critics” who write about everything but understand nothing. I’m talking about reply-guys who make the same 6 tweets about the same 3 subjects. They’re inescapable at this point, yet I don’t see them mocked (as much as they should be)
Like, there was one dude a while back who insisted that women couldn’t be surgeons because they didn’t believe in the moon or in stars? I think each and every one of these guys is uniquely fucked up and if I can’t escape them, I would love to sneer at them.
(2026 is off to a great start, isn't it? Credit and/or blame to David Gerard for starting this.)
For someone that has a bit of a PL/compiler background -- it's not hard if you're familiar with things like this.
What is worrying is that while the fix does address the test case from the issue, it seems there was no analysis performed as to why the failure occurred. Like okay, this test case passes, but I'm not immediately sure the system is now sound.
If it's hard to reason about then it means you as the developer are supposed to sit the fuck down, figure it out, and document it so that it's no longer hard to reason about for someone who reads it. Anything short of that is a cop out.
I'm not going to actually try to figure out how this DI framework works to do this analysis, definitely not for free.