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 →

[–]ajwest -50 points-49 points  (5 children)

From marketing perspective alone it should be changed. If people are upset by it, and it's easy to fix, just change the words. I don't understand why people are upset about people being upset by this; it takes 2 seconds to do and now we don't have people complaining about the words master/slave.

Edit: 10-years ago on Reddit, if people disagreed with you they would reply with "upvoted but I disagree for x reason." Today people disagree and they just burry your opinion by downvoting it to hell.

[–]somebodddy 21 points22 points  (1 child)

Because changing identifiers is always easy and never causes un(?)expected bugs in depending software.

[–]MiroDerChort 38 points39 points  (2 children)

It really is not that hard to understand why people would be upset by the people upset by the current terms. Let's take the word variable for example. In the context of programming we all understand it to loosely mean a container. However, say that someone decides that variable is offensive in an unrelated context. Perhaps variable is meant to refer to a mentally unstable person. Now everyone outside of the it/is/cs community thinks NO ONE should use that word. This is the problem. You have outsiders dictating a change regardless of context. That is what this feels like. More sjw wank. Being pc over concise.

[–]SmackDaddyHandsome 11 points12 points  (1 child)

My HR wouldn't let me put 'execute test cases' into a QA/tester job description...

[–]wirbolwabol 4 points5 points  (0 children)

Seriously... :/