r/coding • • Jun 14 '20

GitHub to replace "master" with alternative term to avoid slavery references | ZDNet

https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/
430 Upvotes

461 comments sorted by

View all comments

Show parent comments

0

u/[deleted] Jun 15 '20

[deleted]

12

u/NightflowerFade Jun 15 '20

Honestly even if it means master and slave, who gives a fuck? It's not like anyone is getting enslaved by the terminology of git.

0

u/[deleted] Jun 15 '20

[deleted]

1

u/NightflowerFade Jun 15 '20

Who is "you guys"? I for one am just an individual. The name is just a meaningless identifier. It could be called the nigger branch for all I care, as long as there is consistency. Changing the name is just a waste of time in the sense of backwards compatibility.

0

u/[deleted] Jun 15 '20

[deleted]

1

u/NightflowerFade Jun 15 '20

Each person makes their own argument with their own nuances. If you evaluate separate viewpoints as a single argument then you risk creating strawmen and arguing against something that the counterparty didn't say in the first place.

0

u/[deleted] Jun 15 '20

[deleted]

5

u/NightflowerFade Jun 15 '20

Then you guys should just lead with that. If you want to fight against what you guys see as "PC" culture then just do it instead of just beating around the bush with bad attempts at mental gymnastics.

I was specifically addressing this paragraph, in which you are arguing against something that I did not say at all.

1

u/Esseratecades Jun 15 '20

Do you want to fight against what you see as PC culture?

3

u/MB1211 Jun 15 '20

Well how the fuck does it have anything to do with slaves? It simply doesn't and until now I've never ever heard of anyone that thought it did. Because it doesn't. It's really absurd. Call it what you want but don't claim master has anything to do with slaves.

1

u/CreativeGPX Jun 15 '20

I'm not really sure why you think one person making an argument has to use terms consistently with another person making a different argument. ... There can be more than one angle to look at something that each leads to the same conclusion. Those different ways can be totally independent of each other. They may also appeal to different kinds of people or be useful in different aspects of the argument because they emphasize different parts. You have to handle each person and argument on its own.

Arguably, the comment you were replying to is a more refined version of the other argument you're citing. The "master-apprentice" argument is saying that "master" is used in harmless ways that don't involve slaves, so we shouldn't act as though "master" automatically implies and is the same as slavery. Meanwhile, the argument you were responding to was saying that not only are there other definitions that makes sense, but that the definition that makes the most sense doesn't even have a built-in notion of an inferior (e.g. slave, apprentice) and that it shows up an areas where "master-slave" terminology has been less prevalent than computers.

In this sense, while certain people probably thought of that definition all along (that's certainly closer to how I thought of it), the solution could just be that documentation, messages, etc. emphasize that definition of master. In the end, as they were learning git 90% of people probably haven't thought twice about what the underlying definition of master was they were probably too busy learning what the definition in this particular context would be. So, we're probably in a pretty good place to frame master in the way that we want rather than having to battle a bunch of people who think of it as meaning one thing or another.

0

u/[deleted] Jun 15 '20

[deleted]

1

u/CreativeGPX Jun 15 '20 edited Jun 15 '20

Your argument seems disingenuous since we're not talking about "changing master and slave", since slave isn't involved.

However, I'd argue that it's substantially less work. Changing documentation and messages is easy and relatively centralized and it would likely also have to be done if you change from the convention of using master. So, it's already the same amount of work before you include that changing the norm of using "master" involves many established projects being changed, the potential for any tools/scripts/etc that assume the near ubiquitous meaning of "master" to break and the need for developers spanning the world to all break their habit of using that terminology. Changing from master is a substantial amount of work relative to just formally clarifying what we mean by master as totally unrelated to "slave" which is why people who see it as a non-issue anyways are especially bothered by the proposal.