If "Master/Slave" terminology in computing sounds bad now, why not change it to "Dom/Sub"?
It sounds way less offensive to those who decry the original terminology's problematic roots but still keeps its meaning intact.
You are viewing a single comment
Honestly, while the controversy is incredibly stupid, it's not something to get worked up about. Not good for your heart 😜
You don't have to relabel anything, just keep using old names for old stuff and maybe consider switching to main for your next GitHub project? It's honestly not that big of a deal.
It's all good and well until you start working in a repo that has both master and main branches for some reason, and it is not clear which is actually the master/main branch.
Then you're working in an idiotic repo. You could just as well have have a master and an actual_master branch. Similar idiocy.
It only takes one person to fuck it up. I agree it's stupid, but introducing a conflicting standard increases the chances of someone fucking it up in the name of progressiveness. Needless to say I killed off the main branch that someone one had tried to make to replace the master branch.
A place I used to work at had that.. The corp had rolled out a non-delete policy with something akin to
*master, so when someone made aabrv_masterbranch it got protected and couldn't be deleted anymore.I work for s company that suddenly asked to rename a lot of stuff. This had consequences. It cost time, money, and created a disconnect between internal to the dev vocabulary that couldn’t be changed easily and user facing vocabulary. Also we were lucky but this could gave broken some long used API that we are proud not to version because the policy we have internally is “we will NEVER break the API”. And so far, for 8 years we still haven’t.
That's why I said to not rename existing stuff, but to consider changing default names for new things. Or don't. It's not the end of the world.
This