A lot of companies seem to be doing this, personally I think trying to make a connection between race and tech is a bit far fetched. Nobody thinks of race when talking about whitelists and blacklists…
In public repos where these changes are merged in to FOSS projects, they get little resistance too - although I could see concern of a potential backlash if anyone questioned the alleged benefit of such a change.
Imagine if this approach was taken with the (now outdated) IDE interface? Instead of “Primary Master, Primary Slave, Secondary Master, Secondary Slave”, there’d maybe be “Primary Primary, Primary Secondary, Secondary Primary, Secondary Secondary” 😵
A lot of companies seem to be doing this, personally I think trying to make a connection between race and tech is a bit far fetched. Nobody thinks of race when talking about whitelists and blacklists…
In public repos where these changes are merged in to FOSS projects, they get little resistance too - although I could see concern of a potential backlash if anyone questioned the alleged benefit of such a change.
Imagine if this approach was taken with the (now outdated) IDE interface? Instead of “Primary Master, Primary Slave, Secondary Master, Secondary Slave”, there’d maybe be “Primary Primary, Primary Secondary, Secondary Primary, Secondary Secondary” 😵
kill all children
Oh yes the reason task manager ends tasks instead of killing now
Oh yes the reason task manager ends tasks instead of killing now
Hasn’t Kubernetes already replaced master-slave with master/manager-worker? Seems like there are plenty of alternatives.
Manager-worker seems classist and problematic /s
That does sound like a very sensible alternative given the context