On Redis master-slave terminology (2018)

Re:On Redis master-slave terminology (2018) by luckylion on Saturday June 13, 2020 @10:29AM (#23509587)

Which means that the perpetually offended will dictate name changes every other year. If somebody argues that they cannot use $software because it contains $word as a variable in its source code somewhere, it's certainly not a good idea to argue with them. It also not a good idea to appease them by doing what they ask.

Maybe developers should steer clear of Twitter so they don't get exposed to the problem. The only winning move is not to play, much like with ads. You don't train yourself to ignore ads or to not be influenced by them, you just use an ad blocker.

[ Parent | on HN ]

Re:On Redis master-slave terminology (2018) by Pfhreak on Saturday June 13, 2020 @11:02AM (#23509874)

Yeah? I don't see evidence that every two years a new word gets brigaded in source code. Do you have examples of projects this has been happening to? If not, this seems like a slippery slope fallacy.

[ Parent | on HN ]

Re:On Redis master-slave terminology (2018) by luckylion on Saturday June 13, 2020 @11:07AM (#23509935)

You're right, master/slave and the new blacklist/whitelist demands did not have two years between them, not even this post is two years old.

[ Parent | on HN ]

Re:On Redis master-slave terminology (2018) by Pfhreak on Saturday June 13, 2020 @11:13AM (#23509977)

Both of those have been discussions for much longer than two years. There's at least a decade of discussions around those two examples.

Edit: closer to two decades - in 2003 LA asked electronics manufacturers not to use the language. Presumably this was first discussed by the community. In the mid aughts, Microsoft was using allowlist/deny list.

So, hardly a recent phenomena, and certainly not every two years. Yes, some projects have been faster or slower to adopt replacements for these terms, which is why you have seen a few discussions in the past few weeks on HN.

[ Parent | on HN ]