Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ZFS Removes References to Slavery

github.com

Post reply on HN
Print view View original

11–20 of 154 posts

Re: ZFS Removes References to Slavery

#11

Post by dsabanin »

ngcazz wrote: post #3
ThrowawayBandit wrote: post #2

I invite people to read about the Chinese Cultural Revolution and the so-called Red Guards. We are getting there. Be very careful what you say and what exact terms you use.

God forbid making concessions for the sake of empathy with people.

I think this is a new version of “think of the children” cliché, used to justify lots of questionable things for ages.

Re: ZFS Removes References to Slavery

#13

Post by ashtonkem »

ThrowawayBandit wrote: post #2

I invite people to read about the Chinese Cultural Revolution and the so-called Red Guards. We are getting there. Be very careful what you say and what exact terms you use.

This is such a hyperbolic response that it’s hard to actually engage with it; I’m not sure that this is helping the conversation at all.

Re: ZFS Removes References to Slavery

#17

Post by mrbonner »

I created an automated tool to deploy and provision Hadoop YARN cluster at work. I’m so glad that I named the non-master hosts “core” nodes instead of slave node :) or I would have to change the naming convention now. I still have the “master” node though.

Re: ZFS Removes References to Slavery

#19

Post by speedgoose »

I think this is a good thing. I'm not a fan of removing the master name, because master has more meanings than in the slavery context and its other meanings fit well the metaphor of master in IT. But they have not removed the master term. Only the slave term, which can go away. I will not miss it, it always felt weird to use this metaphor.

Re: ZFS Removes References to Slavery

#20

Post by ashtonkem »

rvz wrote: post #4

Is Linux going to be next? Let's ask Mr Torvalds nicely to remove all master / slave references in the Linux kernel because it is 'offensive'. /s I don't think such a request is practical given the kLOCs of those references which will break other software.

My general take has been that we should probably avoid these terms moving forward, but that the technical cost of going through nearly a century’s worth of technical stack and fixing every last reference is probably a pretty technically risky operation.
Post reply on HN