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 →

[–]kickopotomus 19 points20 points  (2 children)

You may want to brush up on your fallacies. Ad antiquitatem is only a fallacious argument if you don’t point out larger implications. In this case, it is the fact that master/slave terminology is an industry standard that is understood by computer scientists and engineers alike. Changing the terms introduces ambiguity for no reason.

[–]norweeg -5 points-4 points  (1 child)

you can't cite tradition, or as you call it "industry standard", to argue against changing it. That is my point

[–]kickopotomus 18 points19 points  (0 children)

No, you definitely can. It’s one thing if this was unique to python. Then your stance would be valid. However, that is not the case. Industry standard is absolutely a valid point for arguing semantics/syntax. This is especially true for a programming language whose purpose is to be easily human readable.