Stubsack: weekly thread for sneers not worth an entire post, week ending Sunday 27 October 2024
https://awful.systems/post/2668740
=> More informations about this toot | More toots from froztbyte@awful.systems
guest star of recent sneers kache is at it again
=> More informations about this toot | More toots from froztbyte@awful.systems
just imagine the kinda thinking that goes into even “I can make this post for fun, that’ll be a gas”
=> More informations about this toot | More toots from froztbyte@awful.systems
Dude is about 3 years too late but I guess it’s always 8 o’clock in the outrage store.
For reference, HN went wild on this submission from a pretty obvious 4chan troll (the self-described “Black developer” just so happened to include references to a Stormfront post (since removed)):
news.ycombinator.com/item?id=26487854
=> More informations about this toot | More toots from gerikson@awful.systems
Update: The QRTs are mainly sneering, but this one’s particularly good
=> More informations about this toot | More toots from BlueMonday1984@awful.systems
This guy would be a lot happier if someone had given him a bag of weed and introduced him to college football fandom when he was 12.
=> More informations about this toot | More toots from o7___o7@awful.systems
I found the git master branch naming controversy a bit misguided, since to my mind the analogy was more “master copy” or “master recording” than “master of a slave”. This isn’t IDE. Who names their VCS branch “slave”?
Well, I guess that guy does.
=> More informations about this toot | More toots from bitofhope@awful.systems
I found the git master branch naming controversy a bit misguided, since to my mind the analogy was more “master copy” or “master recording” than “master of a slave”. This isn’t IDE. Who names their VCS branch “slave”?
In a better world, this would’ve probably been a solid argument for letting the master/slave naming convention stick around. We don’t live in a better world.
=> More informations about this toot | More toots from BlueMonday1984@awful.systems
the thing is that the git branch naming was only one of the places among many where this was changed, and in many databases (and often other server-subsystem architectures) master/slave terminology was quite present. iirc there are still some that stick by it today (mostly out of direct choice by project maintainers)
it’s the same thing as whitelist/blacklist, vs allowlist/denylist (or others) - when there’s bad shit linked in baggage, and the cost of changing it (by habit and choice) isn’t all that much, there’s not really any reason to hold by the the old loaded shit
harm reduction comes in many forms
=> More informations about this toot | More toots from froztbyte@awful.systems
Yeah. I remember when the company I used to work for switched our style guide to allowlist/denylist and apart from That One Guy the overall reaction was a big “eh? sure, whatever”. Nobody is out here pretending that this kind of change is going to completely end racism or even that it’s going to have a major impact, but past a certain point continuing to casually throw the memory of chattel slavery around is just cringe.
=> More informations about this toot | More toots from YourNetworkIsHaunted@awful.systems
Note that I was specifically talking about branch names in Git, where it’s debatable if the default name “master” even originated from the master/slave nomenclature.
The problematic nature of the term is a lot more evident in other contexts where a counterpart of the “master” is in fact called a “slave”. Whether that’s reason enough to change the names in any particular instance is not something I’ll comment on.
=> More informations about this toot | More toots from bitofhope@awful.systems
Don’t drink and tweet people.
=> More informations about this toot | More toots from Soyweiser@awful.systems This content has been proxied by September (3851b).Proxy Information
text/gemini