Live data from Hacker News

Redis 4.0

groups.google.com

61–70 of 184 posts

Re: Redis 4.0

#61
post #10

I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.

This terminology has been used for a long time in computing. It's immediately recognised by everyone and in no way endorses human slavery. I'm getting quite fed up of the OTT political correctness movement in tech. Out of interest, what is your opinion on male/female USB connectors? Does one deserve to get fired if they make a joke about "big dongles"?

> I'm getting quite fed up of the OTT political correctness movement in tech.

Is it over the top though? It's a references to a deplorable practice that humans do; why shouldn't we strive for something more civil, and more technically correct? The slave of a database isn't the property of the master and subject to its every whim; it's a replica of the data that can do separate, independent things from the master with that data.

> Out of interest, what is your opinion on male/female USB connectors? Does one deserve to get fired if they make a joke about "big dongles"?

As for gendered connectors, the terms themselves don't carry (or shouldn't :() any judgment nor does it's usage. A valid cable, pipe, &c doesn't have to be heterogeneous/hermaphroditic and can be homogeneous. I would hope that the LGBTQ community wouldn't be offended that only M/F ends can "mate", as biological "mating" (i.e. copulation for the purpose of procreation) can only happen between M and F ends, and see it as a judgment on non-procreation intercourse.

However, if there was an issue about the term M/F being a judgment call, it would be responsible for the community (well, all communities, as the terms M/F for connectors goes beyond just electrical connectors) to listen and (slowly) introduce better names.

There is no reason to make a large portion of the population uncomfortable when it literally costs us nothing to change it (over the long run).

Re: Redis 4.0

#62
post #21
post #11

Earlier quoted context omitted.

Volunteer to fight against ISIS if you really care about abolishing slavery on earth. Edit: Donating to FBM could be a way: http://www.freeburmarangers.org/

Well this post certainly went to hell.

Escalated quickly in a manner I wasn't expecting. Anyway, congrats to antirez on 4.0.

Re: Redis 4.0

#63

I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.

Many hydraulic systems have master and slave cylinder configurations for brake and clutch, for example, in automobiles. I'm afraid that use is ubiquitous and not likely to change.

Re: Redis 4.0

#64
post #3
post #2

LFU policy sounds really interesting!

Thank you, there is more info in this blog post: http://antirez.com/news/109

The point around visualizations for measuring and tuning is an excellent one with a great example. Thanks for the link -- great writeup.

Re: Redis 4.0

#65

Earlier quoted context omitted.

It's pretty "lame" to push established projects to make confusing terminology changes to address whatever words the "peanut gallery" is upset about this week. Try not to be so "uppity", "guy".

"Slave" is technically incorrect. There are better terms to describe the behavior such as "follower" or "replica". If someone has been around long enough to understand what a "slave" is can't figure out what a "replica" or a "follower" does, maybe they shouldn't be in tech. The transition cost for documentation is essentially zero. Naming things is hard, and better names are better for everyone. Antirez said he would…

I agree that the terminology doesn't matter, but consensus does. Master/slave are the commonly understood terms.

Here's a question: if "slave" is offensive, should "kill" (as in 'kill 69' to kill a process in SQL Server) be considered offensive as well? Simply as a consequence of being something 'bad/immoral'? I'm sorry, and I'd be glad to be corrected, but I genuinely find this argument...disingenuous. And people who see things the same way I do see that kind of argument and think that you've got other motives.

EDIT: I want to say (to prevent this discussion from flying off into Trump-land) that I'm liberal on most issues except gun control. I just have a hard time relating to the 'micro-aggression-y' brand of liberalism I've been seeing of late.

Re: Redis 4.0

#67

Earlier quoted context omitted.

Considering how meaningless words are, they seem to have quite an effect on on you... I'm pretty sure your suffering would be alleviated if people chose to respect others' claims if injuries, at least in cases where the cost of doing so is absolutely zero. You can't pretend that there is absolutely no case for people to be upset with this naming scheme. Politics, in this case, is only intruding on your valuable "tech…

My changing my tech terminology isn't going to fix systemic racial tensions. It's not going to fix white officers getting away with killing unarmed black civilians. It's not going to fix the mass incarceration of black males due to broken public policy over the last few decades. It's not going to fix systemic policy issues that lead to a higher chance of poverty for minorities, preventing class mobility. Pick the rig…

If it's any consolation, a lot of my peers, myself included, share this view. I wouldn't bother taking any of your valuable time responding to people who refuse to acknowledge your points.

Re: Redis 4.0

#69
post #9

I really wish Redis wouldn't use the "master/slave" terminology. Primary/replica or even Master/replica are better terms. I know I'll probably get flamed for saying this, but it's a pox on a project that I otherwise very much love.

I'm not for the change in terminology at this step, because it is very unfortunate to change the terminology of a project that is here for years, however I tried to use the fact we have this terminology to remind people of what slavery looked (and still looks in certain parts of the world) like, so: 1) We have a SLAVEOF NO ONE command which is very popular. 2) We have a note about slavery here: https://redis.io/comma…

Maybe a simple solution is to leave SLAVEOF in place for compatibility, and implement a REPLICAOF command as a synonym. Update the docs to use the synonym. Not sure what to do about the INFO output, though.
Post reply on HN