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.
Last week's thread
(Semi-obligatory thanks to @dgerard for starting this)
the C reactionaries[*] I know definitely aren’t ok, but that’s not a new condition. the cognitive load of never, ever writing bugs takes its toll, you know?
[*] and I feel like I have to specify here: your average C dev probably isn’t a C reactionary, but the type of fuckhead who uses C to gatekeep systems development definitely is
You (group A) think C is simple, that it can be thought of as portable assembly, that it teaches you how computers actually work, and that it's easy to avoid memory safety errors with good programming discipline, and is therefore fine.
You (group B) think C is deceptively complex, is far removed from current-day real world hardware semantics, abstracts memory in an outdated and overly simplified manner, and that it's very hard for even professionals to write programs that are correct to the extent of equivalent programs in memory safe languages, therefore C shouldn't be use for new software development.
I think C is deceptively complex, is far removed from current-day real world hardware semantics, abstracts memory in an outdated and overly simplified manner, and that it's very hard for even professionals to write programs that are correct to the extent of equivalent programs in memory safe languages, which are some of the features that make C so fun and exciting. Like rawdogging a one night stand!
We are not the same.
Yeah that's the property of C that ensures it will never go away. If you keep telling young men (which most programmers starting out are) that this language is so dangerous, so scary, of course they'll start using it. There's all sorts of rationalizations going on - it's portable, it's performant, it's what the computer is really like - to justify basically driving a fast car without a seatbelt for the sheer thrill of it.
Now to be fair, C really is quite close to what the machine is really like, if by C you mean B and by machine you mean PDP-7.
It's also highly portable in the sense that all twenty or thirty well-formed, standard-compliant and nontrivial C programs ever written can be compiled to a mind-bogglingly huge variety of hardware and OS targets and even work correctly on some of them.
Past a certain point it's a little bit like learning to type on a typewriter. On one hand it forces you to think about certain types of mistakes and forces you to avoid making errors. On the other hand it gives you a whole bunch of trained habits that are either useless or actively harmful once you're working with better tools.
I always suspected that I wasn't a REAL MAN™, but I didn't know that me learning programming through C++ and being like "well this shit sucks, what the fuck, there has to be a better way" was one of the first symptoms.
and like all C things, the specificities of pointer mechanics might mean any one of a number of things and they're all correct
The original statement was clearly meant to dereference a pointer to an object of type "reactionary," but I expected it to return maybe a Yarvin or at least a Catturd
the thrill of UB: you try to dereference a C reactionary but get a lambda calculus neoreactionary instead