Lady in Love @Lady@cat.family

“readable”

when leftists use an antisemitic template but target it at capitalists, what they are saying, at least historically, is not “the capitalists are jews” / “the jews are capitalists” but rather “the antisemites are wrong; it’s not the jews that are the problem, it’s the capitalists”. they are willing to entertain a conspiracy but find the jewish people innocent.

but then the nazis came along and did make those equations, which of course makes it impossible to tell just from the denouncement of capitalists whether some·one is a leftist or a nazi, and the leftists never really figured out how to counter that

anyway this is why you should only hang out with leftists who have developed beyond european leftism because those tropes don’t exactly have currency anywhere else

explained of course by the fact that the people who came up with contemporary antisemitism and the people who came up with contemporary leftism were largely living in the same countries at the same time and responding to the same material conditions

unfortunately co·opting antisemitic tropes while replacing all references to jews with references to capitalism is a long leftist tradition

but WHO is doing this?? WHO???

‹ -:160: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE2 0x81 0x20 0xE2 ›

oh my god they’re doing a naïve replacement of NBSP to SP

if you get a phone number with an area code far from where you live identifying location-targeted scams is a lot easier i gotta say

those WSDOT scammers are really at it huh

i haven’t used pandoc seriously in like five years but i still always check the release notes

currently at the “getting my Clang from Homebrew” stage in my life

@jamey regarding using [0] and not &: this is a stylistic quirk i’ve picked up from Modern C, which takes the opinion that you should always use arrays when you know the pointer is not nullptr, and avoid & whenever possible. this definitely goes against existing practice but at this point i’m kind of inclined to agree? what you conceptually are doing with getline is passing in arrays with one slot each and it’s overwriting that slot. that’s just not how people usually write it.

regarding hardcoding, agreed. honestly i forgot about C23 constexpr while writing this code, and i think it could be cleaned up a fair bit by using it. i may try taking a stab at this.

regarding the indentation, i think that’s actually a bug in gitweb’s syntax highlighting :P

do you have any advice on naming global constants or struct members? this is probably one of the stylistic things i’m least certain about haha