Need to let loose a primal scream without collecting footnotes first? 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.
(Semi-obligatory thanks to @dgerard for starting this.)
Surely it’s better to specify those defaults in the config file and have the system just fail if the necessary flags aren’t present. Having worked in support I can vouch for the amount of suffering that could be avoided if more systems actually failed if some important configuration isn’t in place.
Completely agree. I think this may just be an extension of the “you gotta know what you’re doing to code correctly in C” old school bullshit.
This is my biggest gripe with that nonsense. If you make it hard to do something well, you won’t end up with an elite series of uber-coders because there aren’t enough of those people to do all the programming that people want to be done. Instead you’ll see that much more software engineering done really goddamned badly and despite appearances at the time it turns out there is a maximum amount of shitty software the world can endure.
What’s great is even the very best “just use valgrind lol, lmao” folks make these errors all the time. It’s basically impossible to write correct C code generally — the best we can do is verify subsets of code (c.f. Rust’s
unsafekeyword). The memory-safety CVEs in EXT3/4 are proof of this, IMO, as if there were anyone able to write correct C code today, it would be Ted Ts’o.