24
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Oct 2024
24 points (100.0% liked)
TechTakes
1427 readers
109 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 1 year ago
MODERATORS
Update: The QRTs are mainly sneering, but this one's particularly good
EDIT: Against my better judgment, I'm letting another sidenote come out:
If you wanna encourage people to drop the master/slave naming scheme, this guy probably gave you a good bit of ammo. Changing a random naming scheme is a pretty low-priority task under most circumstances, but it gets a lot more tempting when it lets you distance yourself from people like this
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.
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
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.
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.
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.
This guy would be a lot happier if someone had given him a pound of weed when he was 12 then introduced him to college football fandom.