Hacker News new | ask | show | jobs
by chrismorgan 1 hour ago
When I started using a graphics tablet, long ago, I was confused about why all this stuff was labelled Wacom, and whether it was applicable to me or not, when using a device of another brand. Some parts of it seemed to be, and other parts didn’t? It was very confusing, and a genuine confusion that made me uncertain even in purchasing. (It would be less confusing now because user-facing parts don’t touch the “Wacom” name as much any more.)

Whereas the “master” thing was transparent linguistic nonsense and a strictly-US cultural thing that a few people foisted on the rest of the world because they decided to get offended on behalf of a hypothetical group.

1 comments

We had to refactor all our internal and external documentation from Master -> leader and slave -> subordinate. So you get things like “… in subordinate mode”.

Thankfully the actual code remained the same (because only engineers look at it).

I've seen "slave nodes" renamed to "children nodes". Because a node that exists solely to support another, more important node, has to carry out the orders it receives from that node, must not do anything on its own, and will be terminated and wiped if it diverges from the vision the main node has — yes, it's a child node alright. You see, that's how children are generally treated in our enlightened society, so the new name is now properly evocative, and has no unfortunate implications.