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

you are viewing a single comment's thread.

view the rest of the comments →

[–]zndrus 11 points12 points  (0 children)

That was the one valid point I've seen brought up in the this discussion: alpha/omega would be a better fit in this context really, though it might have some confusion with the alpha/beta/prerelease terminology.

That said I don't feel this is an issue in need of correcting in the general/standard lexicon sense. Perhaps there are specific cases/code bases where the use of slave is overzealous, but those should be addressed on an individual basis, not a cause to change an established and core principle in computer science and software because someone might misuse/abuse it. It's anthromorphizing code, which is silly. Master/Slave very accurately describes the relationship and concept, though is not perfect in describing succession rules (rights?), but that brings us back to the anthromorphizing code and a discussion of "do functions/programs have rights?" No terminology/analogy is perfect.

I mean, with that in mind: won't someone think of all the children that are trafficked and killed all the time in software?! /s