News for hackers. Stuff that matters.
Re:On Redis master-slave terminology by platinumrad on Thursday September 06, 2018 @05:54PM (#17929952)
A huge diff that doesn't mean anything is a nontrivial cost. Documentation would also have to be changed and articles would have to be updated.

Deprecating something, even terminology, should not be done lightly.

[dead]
Re:On Redis master-slave terminology by aiven on Thursday September 06, 2018 @07:05PM (#17930407)
this is how voting works tho
Re:On Redis master-slave terminology by meowface on Thursday September 06, 2018 @07:26PM (#17930535)
In practice, but not on paper. HN guidelines forbid that sort of voting behavior.
Re:On Redis master-slave terminology by grzm on Thursday September 06, 2018 @07:39PM (#17930614)
There is no guideline on HN forbidding down voting for disagreement. 'dang as recently as a month ago reiterated this:

https://news.ycombinator.com/item?id=17666145

Re:On Redis master-slave terminology by meowface on Thursday September 06, 2018 @07:49PM (#17930670)
Ah sorry, not sure where I got that idea from, then. I may've been confused by various subreddit mods establishing rules along the lines of "the downvote is not a disagree button".
Re:On Redis master-slave terminology by dang on Friday September 07, 2018 @05:18AM (#17932896)
Re:On Redis master-slave terminology by jachee on Thursday September 06, 2018 @06:04PM (#17930039)
Sometimes the right thing is nontrivial.
Re:On Redis master-slave terminology by platinumrad on Thursday September 06, 2018 @06:13PM (#17930090)
Maybe. I'm undecided on the issue of changing existing instances of "master-slave", but I would definitely use something else in a greenfield project.

You're getting downvotes not (just) due to disagreements but because your first comment was incorrect (it's not just a sed command) and your second was unproductive.