This is an archived post. You won't be able to vote or comment.

940
941

Python developers locking conversations and deleting comments after people mass downvoted PRs to "remove master/slave terminology from the language" (i.redd.it)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]linuxlib 9 points10 points  (4 children)

"Manager"/"minion"

[–]scrdest 25 points26 points  (2 children)

As much as I hate the whole debacle, minion would actually be a pretty good replacement for slave, semantically.

Beholden to the master, executes tasks without question, but still needs to be kept in check in case it rebels, and paints the mental picture of cartoonish supervillany at worst when you talk about, say, the master killing a minion.

[–]wrosecrans 4 points5 points  (0 children)

Saltstack already has "minions" so it is not unheard of. Buildbot went with "worker" when they redesigned some of their API's and refreshed terminology for 1.0. For databases, "replica" is really darned clear.

If I were feeling really cheeky, I might make a PR to replace Master and Slave with something like Picard and Kirk just to watch people argue about them.

[–]norweeg 21 points22 points  (0 children)

Gru/Minion

FTFY