Live data from Hacker News

LOLWUT: a piece of art inside a database command

antirez.com

61–70 of 127 posts

Re: LOLWUT: a piece of art inside a database command

#61
post #54
post #4

This is exactly the insanity I expect from a man that have been haunted by an internet mob the last past weeks. I like these, Sidekiq also have the tableflip methods (with tests) that does exactly nothing, https://github.com/mperham/sidekiq/blob/927680cae78731c540fe...

There are at least four easter eggs in the Sidekiq source. You've found one. Kudos to antirez for starting this refactoring. Switching to replica will clear up this confusing terminology.

I don't think anyone claimed to find the term confusing. They claimed to find it offensive (mostly on behalf of theoretical others).

Re: LOLWUT: a piece of art inside a database command

#62
post #17

Earlier quoted context omitted.

It makes me very angry when "they" (I'm not even sure who "they" are or what their motives are) go around policing random software projects for political correctness compliance, bullying/mobbing the maintainers if they don't comply, etc. These people even go after your project if one of your maintainers is deemed politically incorrect outside of the scope of the project (i.e. on Twitter) and demand they be kicked out…

> I miss the days when politics and political correctness didn't directly affect software projects. They've always affected software projects, they just haven't affected you . > What do these political police stand to gain from all of this? Making other people feel as welcome in software as you've already been by default.

Not the above poster, but, alas, given some of the behaviour I've seen, I'd no longer be particularly inclined to be welcoming. In some sense, a broad, offensive filter is better than doing it manually. Who cares if it reduces user count or whatever - it makes my life easier.

Perhaps it's a "good" thing I haven't created any major OSS projects...

Re: LOLWUT: a piece of art inside a database command

#63
I've said it before, and I'll say it again. The problem with letting thin skinned people decide what's offensive and what isn't is the list constantly changes, and contradicts itself.

Now there's precedent. Other people's turbulent emotions define what is acceptable in redis, and all you need to do is throw tantrums and say your feelings are hurt.

This is sheer insanity. If the words are that offensive that they should be removed from a computer program, should they be removed from the dictionary next?

Sheer insanity.

Antirez, I sympathize with you. I'm sorry you have to put up with this madness.

Re: LOLWUT: a piece of art inside a database command

#64
post #7

Earlier quoted context omitted.

I'm both aghast and amused that people are making a big deal about master/slave when used in the context of computers.

The way I look at it, the amount of effort required to change that terminology is less than the amount of community discomfort generated by keeping it.

To that I say:

If you think it's that easy, you personally should be the one to do the work to change it.

Now that sounds incredibly snarky, for that I apologise. But it does sum up a lot of people's thoughts towards it, and it's no more snarky that the typical twitter driveby of 'it's just a find/replace'

Anyone who has actually read the author's explanation (not saying you haven't), knows that he would choose different terminology in hindsight, but the work involved in updating documentation, and maintaining protocol compatibility that allows redis to keep its backwards compatibility features it aims for is non-trivial.

Not to mention all the documentation, and also the ongoing responsibility to third party code and infrastructure which relies on the ecosystem, that has to update along with this.

That's all work, constant, ongoing work.

Should they still make this change? Maybe, master/slave isn't exactly accurate.

But my point is that talk is cheap, and the loudest voices seem to be the folks with no willingness to put skin in the game to change it.

If you truly believe it's so trivial, why won't you help with the labour, both initial and ongoing?

Re: LOLWUT: a piece of art inside a database command

#65
post #43

Earlier quoted context omitted.

He’s announcing it (and built it) as a reaction against the master/slave naming issue. It’s a political statement dismissing removal of exclusionary language. Not sure why I’m being downvoted because he’s publicly stated this on Twitter explicitly several times.

Did you read his other blog posts? He is not an exclusionary person, and labeling him as such, based on an impulsive reaction to an abstract word, with multiple contextual interpretations, is a misguided interpretation of recent events. His frustration at irrational demands for unnecessary effort is understandable.

I have read what he’s been writing about this.

By the way, “irrational demands for unnecessary effort” is a value judgment.

Re: LOLWUT: a piece of art inside a database command

#66
post #17

Earlier quoted context omitted.

It makes me very angry when "they" (I'm not even sure who "they" are or what their motives are) go around policing random software projects for political correctness compliance, bullying/mobbing the maintainers if they don't comply, etc. These people even go after your project if one of your maintainers is deemed politically incorrect outside of the scope of the project (i.e. on Twitter) and demand they be kicked out…

> I miss the days when politics and political correctness didn't directly affect software projects. They've always affected software projects, they just haven't affected you . > What do these political police stand to gain from all of this? Making other people feel as welcome in software as you've already been by default.

No, they're making themselves feel righteous, at very little gain to the minorities they're ostensibly protecting. I'm Slavic. The name for my ethnicity literally means, and is the root of the word slave. Shouldn't I have more say than anyone how my ethnic identity as a slave gets bandied about? I say the master/slave terminology is effective, evocative, and useful.

Re: LOLWUT: a piece of art inside a database command

#67
post #22

We seem to be losing our playfulness. In light of that, I'm going to take some time today to do something random, just for fun, and share it with others.

I added this header to all of our http-responses: "X-Clacks-Overhead: GNU Terry Pratchett" Which was proposed by http://www.gnuterrypratchett.com/ and as far as I know no one have noticed :)

I added this to my two HAProxies so everything including my Mastodon instance sends out the clacks.

Re: LOLWUT: a piece of art inside a database command

#68

Ah, hackers, we are getting lost inside capitalism - inside startups - inside e-commerce and social media... I am not talking about socialism or leftism, we can get lost in those too - I am talking about 'personal'/'hobbyist'/'obscure' - like we see in zine sites like whimsy.space or the rabbit hole of sites like philosopher.life. A part of our humanity will always be in 'obfuscation'/'code golf', demoscene, abandonw…

This is so deep that I'll have to take care not to get nitrogen poisoning coming back up.

Re: LOLWUT: a piece of art inside a database command

#69

Ah, hackers, we are getting lost inside capitalism - inside startups - inside e-commerce and social media... I am not talking about socialism or leftism, we can get lost in those too - I am talking about 'personal'/'hobbyist'/'obscure' - like we see in zine sites like whimsy.space or the rabbit hole of sites like philosopher.life. A part of our humanity will always be in 'obfuscation'/'code golf', demoscene, abandonw…

This is so deep that I'll have to take care not to get nitrogen poisoning coming back up.

Apologies for being heavy-handed. Sometimes this happens.

Re: LOLWUT: a piece of art inside a database command

#70

Earlier quoted context omitted.

The way I look at it, the amount of effort required to change that terminology is less than the amount of community discomfort generated by keeping it.

I'll add another point: if the reason to not do this is the effort, then why is effort being put into generative art in redis? To be clear, I think this is neat, and appreciate that antirez can and should add some joy into the world in what ever way they see fit. I'm just playing devil's advocate. With that said, changing terminology is more than just a code change, there's a bunch of documentation, as well as possib…

> I'll add another point: if the reason to not do this is the effort, then why is effort being put into generative art in redis?

Seemed to me like it was a subtle middle finger to the complainers.

Post reply on HN