Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up#22667 replaced occurrences of master/slave terminology with leader/follower #2692
Conversation
added a commit
that referenced
this pull request
May 20, 2014
alex
merged commit 8a95b4f
into
django:master
May 20, 2014
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Thanks for taking the time to do this! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
PunKeel
May 26, 2014
Are you serious ?
The meaning of a word is defined by its use, by the context.
In this case, master/slave is used by every database server, in every documentation (redis, mysql …)
NB: I don't say I'm against this change. Just that I don't see the point of changing two words with two others just because they have been used somewhere else.
For example, your avatar is red. Red, like communism. You should use a black and white color. Oh no, that's linked to racism too. Well. Let's remove colors, too, then ? ;)
PunKeel
commented
May 26, 2014
|
Are you serious ? NB: I don't say I'm against this change. Just that I don't see the point of changing two words with two others just because they have been used somewhere else. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kamilogorek
commented
May 26, 2014
|
Is that a real life? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evildmp
May 26, 2014
Contributor
As you can see from beec056 the terminology we have actually used is "primary/replica". So thank you for your interest, but there's nothing to see here and you can move along now.
|
As you can see from beec056 the terminology we have actually used is "primary/replica". So thank you for your interest, but there's nothing to see here and you can move along now. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jonathan3
May 26, 2014
Before the flood of white male HN dwellers truly kicks off and obliterates all reasonable discussion, I'd like to thank the Django team for taking the time to do this.
jonathan3
commented
May 26, 2014
|
Before the flood of white male HN dwellers truly kicks off and obliterates all reasonable discussion, I'd like to thank the Django team for taking the time to do this. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
wodim
May 26, 2014
i'm just here for the laughs. is IT becoming too stupid? has science gone too far?
wodim
commented
May 26, 2014
|
i'm just here for the laughs. is IT becoming too stupid? has science gone too far? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jleclanche
May 26, 2014
Contributor
Discussion on the ticket: https://code.djangoproject.com/ticket/22667
"Primary" and "Replica" aren't especially bad choices, but they're also wrong. The correct terms are master and slave. They've been used in databases, hardware setups, server setups and god knows what else for god knows how long.
I cannot f_ing believe this PR made it through and was given actual man hours when there are massive outstanding PRs and patches on trac that need real attention. And don't be surprised that this does make it on HN and probably later on the usual slashdot/phoronix and what not. This is stupid *and_ controversial which is exactly what tech media loves.
And to the HN/whatever crowd, don't post stupid memes here. This isn't the place.
Help yourselves and revert this, guys. Django docs, or docs in general are not the place to make up new terms for stuff that already exists.
PS: Quick heads up: This made it to 4chan and various other troll places. Do not be surprised if there's suddenly an influx of .. weird comments.
|
Discussion on the ticket: https://code.djangoproject.com/ticket/22667 I cannot f_ing believe this PR made it through and was given actual man hours when there are massive outstanding PRs and patches on trac that need real attention. And don't be surprised that this does make it on HN and probably later on the usual slashdot/phoronix and what not. This is stupid *and_ controversial which is exactly what tech media loves. And to the HN/whatever crowd, don't post stupid memes here. This isn't the place. Help yourselves and revert this, guys. Django docs, or docs in general are not the place to make up new terms for stuff that already exists. PS: Quick heads up: This made it to 4chan and various other troll places. Do not be surprised if there's suddenly an influx of .. weird comments. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jardaroh
May 26, 2014
This is silly.
Next we will remove all mention og objects because some people might feel objectified.
Or classes, because of the poor people that feels they are being discriminated against.
Sure, I understand that the use of words can hurt, but words themselves carry no meaning outside of it's use. Saying a car is yellow and calling a person yellow are two very different statements. We seem to have a new round of book burnings going on today...
jardaroh
commented
May 26, 2014
|
This is silly. Sure, I understand that the use of words can hurt, but words themselves carry no meaning outside of it's use. Saying a car is yellow and calling a person yellow are two very different statements. We seem to have a new round of book burnings going on today... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Gwildor
May 26, 2014
Guys, just ignore this. These are bots who do this automatically for projects, which have been circling around on Github lately. There are also ones about feminism etc. The Linux kernel also had a PR like this a few months ago with a massive amount of responses on it.
Don't feed the trolls, and just continue to use master and slave.
Gwildor
commented
May 26, 2014
|
Guys, just ignore this. These are bots who do this automatically for projects, which have been circling around on Github lately. There are also ones about feminism etc. The Linux kernel also had a PR like this a few months ago with a massive amount of responses on it. Don't feed the trolls, and just continue to use |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ajgon
May 26, 2014
Faith in humanity restored. Thank you guys. I just want to add, that this will also be bad for django itself, since almost every developer who is no aware of this will be confused, and trust me - he will be expecting that this is some bizarre django thing, not the well known pattern. Peace.
ajgon
commented
May 26, 2014
|
Faith in humanity restored. Thank you guys. I just want to add, that this will also be bad for django itself, since almost every developer who is no aware of this will be confused, and trust me - he will be expecting that this is some bizarre django thing, not the well known pattern. Peace. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lynncyrin
commented
May 26, 2014
|
Thanks so much Django for doing this thing! <3 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
gregferrell
commented
May 26, 2014
|
Good move. Thank you. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Thesoro
commented
May 26, 2014
|
Excellent stuff. Thanks for doing that. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lynncyrin
May 26, 2014
I'm very glad for this change because as a PoC I felt very uncomfortable seeing and using this terminology in my code
lynncyrin
commented
May 26, 2014
|
I'm very glad for this change because as a PoC I felt very uncomfortable seeing and using this terminology in my code |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Ragzouken
commented
May 26, 2014
|
glad to see big projects taking this seriously |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kittenpies
May 26, 2014
Thanks Django for making this important change to be more welcoming and inclusive to more members of the tech community. <3
kittenpies
commented
May 26, 2014
|
Thanks Django for making this important change to be more welcoming and inclusive to more members of the tech community. <3 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
northofnormal
May 26, 2014
"they've always been called that" is a dumb reason to keep doing something, especially something that is hurtful or alienating. Kudos to Django for making this change!
northofnormal
commented
May 26, 2014
|
"they've always been called that" is a dumb reason to keep doing something, especially something that is hurtful or alienating. Kudos to Django for making this change! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
dstaley
May 26, 2014
The use of the terms master and slave in relation to databases (and hardware configurations) has always made me uncomfortable. I think the terms leader and follower are much more appropriate, and are actually more expressive.
dstaley
commented
May 26, 2014
|
The use of the terms |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tingley
May 26, 2014
These terms have been in use forever, but that doesn't make them good. Fixing them has to start somewhere; good for Django for taking the lead.
tingley
commented
May 26, 2014
|
These terms have been in use forever, but that doesn't make them good. Fixing them has to start somewhere; good for Django for taking the lead. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
copumpkin
commented
May 26, 2014
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
RobotDisco
commented
May 26, 2014
|
Wow, this is awesome! Thanks! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
gesa
commented
May 26, 2014
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
selenamarie
commented
May 26, 2014
|
Thanks @fcurella! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
maban
commented
May 26, 2014
|
Thank you! :) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
joliss
commented
May 26, 2014
|
Awesome change, thanks @fcurella! "Primary/replica" sounds much better. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ghost
commented
May 26, 2014
|
Excellent. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
clundie
commented
May 26, 2014
|
Good. The old terminology should be made obsolete. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Thank you so much for making this change! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
fhocutt
commented
May 26, 2014
|
Good change! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
polymerwitch
commented
May 26, 2014
|
Awesome change. Another reason to love the Django project :) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
coderanger
commented
May 26, 2014
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rivalee
commented
May 26, 2014
|
Good change, thank you! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
fujin
commented
May 26, 2014
|
Great work. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
onoffleftright
May 26, 2014
Excellent change! Actually dealing with a database replication issue myself right now. Semantics matter; even in technical documentation. I'll be using "primary" and "replica" from here on out.
onoffleftright
commented
May 26, 2014
|
Excellent change! Actually dealing with a database replication issue myself right now. Semantics matter; even in technical documentation. I'll be using "primary" and "replica" from here on out. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
drcable
May 26, 2014
Language changes through use. We have a chance to change language for the better(or at least, less-racist. I imagine there are people in this thread who don't think that's better), and we're taking it.
This is great work by django
drcable
commented
May 26, 2014
|
Language changes through use. We have a chance to change language for the better(or at least, less-racist. I imagine there are people in this thread who don't think that's better), and we're taking it. This is great work by django |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nslater
commented
May 26, 2014
|
We switched to |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
joestump
May 26, 2014
@evildmp I'm
joestump
commented
May 26, 2014
|
@evildmp I'm |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ghost
commented
May 29, 2014
|
@krainboltgreene I bet you i will. $100.000. Terribly written framework anyways. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
dalu
May 29, 2014
The Django masters are also deleting comments that they don't like.
The Djangoists are the real slavers
dalu
commented
May 29, 2014
|
The Django masters are also deleting comments that they don't like. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mowings
May 29, 2014
The most interesting thing about this PR is the sheer amount of furor generated. Sure, the changes to the docs basically solve a non-existent problem. At the same time, the new terms aren't exactly confusing either. While I'd prefer master || primary -> replica || slave || secondary, I don't recall anybody getting this excited over Zookeepers followers and leaders. [Edit: missed the change to primary/replica]
Maybe it's generational -- y'all are all just so ... verbal.
mowings
commented
May 29, 2014
|
The most interesting thing about this PR is the sheer amount of furor generated. Sure, the changes to the docs basically solve a non-existent problem. At the same time, the new terms aren't exactly confusing either. While I'd prefer master || primary -> replica || slave || secondary, I don't recall anybody getting this excited over Zookeepers followers and leaders. [Edit: missed the change to primary/replica] Maybe it's generational -- y'all are all just so ... verbal. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jm3
commented
May 29, 2014
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
vnaylon
May 29, 2014
Great change. The argument that “it’s been that [wrong/offensive] way forever” is not sufficient.
vnaylon
commented
May 29, 2014
|
Great change. The argument that “it’s been that [wrong/offensive] way forever” is not sufficient. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jberkus
May 29, 2014
FWIW, the PostgreSQL project has always used the terms "master" and "standby" to refer to a single-master system, throughout our documentation. For that matter, other DBMSes with single-master replication use the terms "Primary/Replica" and "Primary/Secondary" -- more than use the terms "Master/Slave", which are used more frequently to refer to antique HDD configurations under IDE. So the assertion that the "industry standard" is "Master/Slave" is demonstrably false.
jberkus
commented
May 29, 2014
|
FWIW, the PostgreSQL project has always used the terms "master" and "standby" to refer to a single-master system, throughout our documentation. For that matter, other DBMSes with single-master replication use the terms "Primary/Replica" and "Primary/Secondary" -- more than use the terms "Master/Slave", which are used more frequently to refer to antique HDD configurations under IDE. So the assertion that the "industry standard" is "Master/Slave" is demonstrably false. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ghost
May 29, 2014
I disagree with this because, you know, when master tells slave to do something he ought to do it, no objections. While the terms leader/followers are more politically correct, they do not serve as effectively as master/slave.
ghost
commented
May 29, 2014
|
I disagree with this because, you know, when master tells slave to do something he ought to do it, no objections. While the terms leader/followers are more politically correct, they do not serve as effectively as master/slave. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lysenko
May 29, 2014
Github must ban the government of Mauritania.
http://www.npr.org/programs/specials/racism/010828.mauritania.html
Cite:
The government goes to great lengths to deny the problem. It has banned the word "slave" from use by the media, and foreign journalists risk arrest and deportation for investigating the issue.
lysenko
commented
May 29, 2014
|
Github must ban the government of Mauritania. The government goes to great lengths to deny the problem. It has banned the word "slave" from use by the media, and foreign journalists risk arrest and deportation for investigating the issue. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
davidcelis
May 29, 2014
While the terms leader/followers are more politically correct, they do not serve as effectively as master/slave.
@mannol1 Irrelevant. The terms being used are primary/replica. Please read the entire discussion before contributing.
davidcelis
commented
May 29, 2014
@mannol1 Irrelevant. The terms being used are primary/replica. Please read the entire discussion before contributing. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
zerkms
May 29, 2014
@davidcelis to be honest - replica term (from my perspective) means that something is identical to something else.
Whereas the slave server doesn't have to be so. It's frequent the slave server only holds part of the master server data.
Finalizing: the slave term expresses a role, whereas the replica term expresses the data attribute/quality.
IE: slave server in mysql replication schema may hold NO DATA at all. I wouldn't call it replica in this case, just because it's not.
zerkms
commented
May 29, 2014
|
@davidcelis to be honest - Whereas the Finalizing: the IE: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
d1ffuz0r
May 29, 2014
@mannol1 >While the terms leader/followers are more politically correct
Absolutely incorrect for Europe. Such double standards
d1ffuz0r
commented
May 29, 2014
|
@mannol1 >While the terms leader/followers are more politically correct |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
karlht
May 29, 2014
Thank you to the Django developers -- leader/follower reads with much less baggage attached for me.
karlht
commented
May 29, 2014
|
Thank you to the Django developers -- leader/follower reads with much less baggage attached for me. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
eliziario
May 29, 2014
I really don't care. Call it sun/earth, smurgasbordnic/flatuvalicxlkt, remove the feature, delete the documentation. I don't care, but please, just stop. All conceivable POVs have already been exposed ad nauseam.
eliziario
commented
May 29, 2014
|
I really don't care. Call it sun/earth, smurgasbordnic/flatuvalicxlkt, remove the feature, delete the documentation. I don't care, but please, just stop. All conceivable POVs have already been exposed ad nauseam. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ghost
May 29, 2014
If only this sort of interest formed around more meaningful issues. Development should be free from political and social obligations and as such this is not much more than an end-user confusing step. On the other hand why not, if it pleases someone - it's just syntax.
ghost
commented
May 29, 2014
|
If only this sort of interest formed around more meaningful issues. Development should be free from political and social obligations and as such this is not much more than an end-user confusing step. On the other hand why not, if it pleases someone - it's just syntax. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lukecarbis
May 30, 2014
Should I make a PR for this, too? https://github.com/lukecarbis/django/compare/patch-1
lukecarbis
commented
May 30, 2014
|
Should I make a PR for this, too? https://github.com/lukecarbis/django/compare/patch-1 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andr0s
May 30, 2014
Do you guys know why this silly commit got so many negative comments? I
will tell you why.
Because people tired of propaganda. Politicians tell us what we should and
should not do, how we should think about some things and should not. They
promote craziest fanatics on media which claim that, say, "men" sounds
discriminative and should be banned. If you guys are white Americans
(French\Spanish\whoever) then why the f_ck you should be responsible for
what your grand-grand-grand-parents did? Even worse - if your parents moved
to the US after the slavery had been destroyed then why the f_ck you should
feel any kind of blame? You have all just been brainwashed. You are judged
for the crime you did not commit. And the worst thing is that you agreed
with that.
And it all turns into such a stupid thing as this commit.
Do you know who are real slaves now? You. Those who say 'okaaay' when some
sly people tell you what you should think and do.
Don't be sissy, fight for your freedom!
2014-05-30 7:48 GMT+07:00 Luke Carbis notifications@github.com:
Should I make a PR for this?
https://github.com/lukecarbis/django/compare/patch-1Reply to this email directly or view it on GitHub
#2692 (comment).
andr0s
commented
May 30, 2014
|
Do you guys know why this silly commit got so many negative comments? I Because people tired of propaganda. Politicians tell us what we should and And it all turns into such a stupid thing as this commit. Do you know who are real slaves now? You. Those who say 'okaaay' when some Don't be sissy, fight for your freedom! 2014-05-30 7:48 GMT+07:00 Luke Carbis notifications@github.com:
|
CodeOtter
referenced this pull request
May 30, 2014
Closed
Replaced occurances of the word "black" with something less racially insensitive #2745
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
isotopp
commented
May 30, 2014
|
I think we need to reform Python and its use of WHITEspace. This is all wrong. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Dundee
May 30, 2014
I think you should rename Django to something less offensive, because it can reffer to movie "Django Unchained" which contains slaves and violence!
You should take example from http://www.vislab.uq.edu.au/nb/jokes/computers/pc_unix.html and take this seriously.
Dundee
commented
May 30, 2014
|
I think you should rename Django to something less offensive, because it can reffer to movie "Django Unchained" which contains slaves and violence! You should take example from http://www.vislab.uq.edu.au/nb/jokes/computers/pc_unix.html and take this seriously. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
MattWindsor91
May 30, 2014
I don't see how preferring the original terms is fallacious. In terms of documentation, it is genuinely confusing for documentation users to use terminology different from that which they're used to.
One could argue that some people here have been using the appeal to novelty =p
MattWindsor91
commented
May 30, 2014
|
I don't see how preferring the original terms is fallacious. In terms of documentation, it is genuinely confusing for documentation users to use terminology different from that which they're used to. One could argue that some people here have been using the appeal to novelty =p |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
haasip-satang
May 30, 2014
Don't you think this also reads a lil funny then: "Let's remove the terminology master and slave and merge our changes into django:M A S T E R" ;) Maybe you should change the branch name too (or is that ok because there are no slave branches ;-P ? )
haasip-satang
commented
May 30, 2014
|
Don't you think this also reads a lil funny then: "Let's remove the terminology master and slave and merge our changes into django:M A S T E R" ;) Maybe you should change the branch name too (or is that ok because there are no slave branches ;-P ? ) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
canweriotnow
May 30, 2014
Please. It is a valuable contribution.
On May 29, 2014 8:48 PM, "Luke Carbis" notifications@github.com wrote:
Should I make a PR for this?
https://github.com/lukecarbis/django/compare/patch-1—
Reply to this email directly or view it on GitHub
#2692 (comment).
canweriotnow
commented
May 30, 2014
|
Please. It is a valuable contribution.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lemontooth
May 30, 2014
@CaptainHayashi
In terms of documentation, it is genuinely confusing for documentation users to use terminology different from that which they're used to.
Oh come on. How is that going to confuse anyone? People that dense won't make it through the tutorial anyway, let alone using multiple databases. If anything, the change makes the documentation more descriptive. And for "no one will be able to discover this", google "django master slave" and look at the first hit. Just the snippet provides you with enough information. Also this.
to be honest - replica term (from my perspective) means that something is identical to something else.
And that is what it describes, literally, in the context of this change (not accounting for lag/sync problems).
"Let's remove the terminology master and slave and merge our changes into django:M A S T E R" ;) Maybe you should change the branch name too (or is that ok because there are no slave branches
How original. But yes, you are correct, this was about the compound "master-slave" only.
lemontooth
commented
May 30, 2014
|
@CaptainHayashi
Oh come on. How is that going to confuse anyone? People that dense won't make it through the tutorial anyway, let alone using multiple databases. If anything, the change makes the documentation more descriptive. And for "no one will be able to discover this", google "django master slave" and look at the first hit. Just the snippet provides you with enough information. Also this.
And that is what it describes, literally, in the context of this change (not accounting for lag/sync problems).
How original. But yes, you are correct, this was about the compound "master-slave" only. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
GrueMaster
May 30, 2014
Oddly, the term is used in a lot of industries to describe a controller/dummy relationship. The railroad industry has used them for as long as they used multiple locomotives to move cargo.
If we are going to be eliminating the term Master, what will replace the title of the college degree beyond Bachelor, but before Doctorate? How about the title of a higher ranked chess player or the head of a college?
How about the phrase "he's a slave to his work" often meaning that he lets his work come before his personal life? What about remote control systems? Will we be renaming these communication links too?
And lets not forget the religious implications. People that are devout are considered slaved to their master (God).
Interesting responses on stackoverflow.com regarding this topic. One poster suggests using "pimp/ho".
This entire topic is rubbish, and I find it offensive.
GrueMaster
commented
May 30, 2014
|
Oddly, the term is used in a lot of industries to describe a controller/dummy relationship. The railroad industry has used them for as long as they used multiple locomotives to move cargo. If we are going to be eliminating the term Master, what will replace the title of the college degree beyond Bachelor, but before Doctorate? How about the title of a higher ranked chess player or the head of a college? How about the phrase "he's a slave to his work" often meaning that he lets his work come before his personal life? What about remote control systems? Will we be renaming these communication links too? And lets not forget the religious implications. People that are devout are considered slaved to their master (God). Interesting responses on stackoverflow.com regarding this topic. One poster suggests using "pimp/ho". This entire topic is rubbish, and I find it offensive. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
canweriotnow
commented
May 30, 2014
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
gngeal
May 30, 2014
It is incredibly US-centric to assume that "master/slave" are "racially charged terms". There have been many societies where slaves and freemen were not separated along racial or ethnic lines, for example, the Roman Empire. Witness the cultural imperialism face of the PC movement at its finest!
gngeal
commented
May 30, 2014
|
It is incredibly US-centric to assume that "master/slave" are "racially charged terms". There have been many societies where slaves and freemen were not separated along racial or ethnic lines, for example, the Roman Empire. Witness the cultural imperialism face of the PC movement at its finest! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
lemontooth
May 30, 2014
If we are going to be eliminating the term Master
[yadda yadda about how it is impossible to nuke "master" from the english language]
Fine, but this PR wasn't about any of that. It was very specifically about replacing "master/slave" with "primary/secondary" in the Django documentation on Multiple Databases, terms that are more descriptive and widely used. "Master" is still used in other contexts than database replication in the documentation. Nobody expressed a desire to change the term for higher ranked chess players.
Interesting responses on stackoverflow.com regarding this topic. One poster suggests using "pimp/ho".
This entire topic is rubbish, and I find it offensive.
Yes, very interesting. Thanks for sharing. Much constructive.
Witness the cultural imperialism face of the PC movement at its finest!
Now that is some kind of fresh madness.
lemontooth
commented
May 30, 2014
Fine, but this PR wasn't about any of that. It was very specifically about replacing "master/slave" with "primary/secondary" in the Django documentation on Multiple Databases, terms that are more descriptive and widely used. "Master" is still used in other contexts than database replication in the documentation. Nobody expressed a desire to change the term for higher ranked chess players.
Yes, very interesting. Thanks for sharing. Much constructive.
Now that is some kind of fresh madness. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tamamoe
commented
May 31, 2014
|
What's going on here? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Frogging101
May 31, 2014
Ugh, this is bullshit. Why should anyone give a damn about the terminology? Keep your feels out of computing.
Frogging101
commented
May 31, 2014
|
Ugh, this is bullshit. Why should anyone give a damn about the terminology? Keep your feels out of computing. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Frogging101
May 31, 2014
Also, when did the social justice army invade GitHub? Nowhere is safe anymore.
Frogging101
commented
May 31, 2014
|
Also, when did the social justice army invade GitHub? Nowhere is safe anymore. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
minexew
May 31, 2014
@Frogging101 Running around the Internet spouting incoherent subjective arguments to make oneself feel beneficial to the society is easier than writing good code.
As if you forgot to realize how stupid the average person is and that half of the population is by definition dumber than that. GitHub has no access barriers, making it very susceptible to attacks from SJW and their sheep. Try the same on LKML and you'll get blown out in minutes.
minexew
commented
May 31, 2014
|
@Frogging101 Running around the Internet spouting incoherent subjective arguments to make oneself feel beneficial to the society is easier than writing good code. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
wlipa
May 31, 2014
The true master here is a kind of linguistic puritanism to which, unfortunately, many are slavishly devoted.
wlipa
commented
May 31, 2014
|
The true master here is a kind of linguistic puritanism to which, unfortunately, many are slavishly devoted. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
conatus
commented
Jun 1, 2014
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
distransient
commented
Jun 2, 2014
|
Forget all the openly bigoted opinions ITT; this is a great PR! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Tak
commented
Jun 2, 2014
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
6079-Smith-W
Jun 2, 2014
"master/slave" is ungood crimethinkful oldspeak. plusgood rectify unword.
Is Minitrue doubleplusgoodwork truthwise. chocorat anyone?
6079-Smith-W
commented
Jun 2, 2014
|
"master/slave" is ungood crimethinkful oldspeak. plusgood rectify unword. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
celber
Jun 9, 2014
Hi, i feel personally offended by racist name of this repo while it associates with tragic story of one american slave. I demand changing its name to "My Web Pony".
celber
commented
Jun 9, 2014
|
Hi, i feel personally offended by racist name of this repo while it associates with tragic story of one american slave. I demand changing its name to "My Web Pony". |
fcurella commentedMay 20, 2014
The docs and some tests contain references to a master/slave db configuration.
While this terminology has been used for a long time, those terms may carry racially charged meanings to users.
This patch replaces all occurrences of master and slave with 'leader' and 'follower'