I think as software developers we're notoriously bad at naming things, and this particular terminology falls firmly under the umbrella of "bad names for things".
The insistence of folks to cleave to (and argue for) these outdated and poorly chosen names is foolish, regardless of the reason.
If there's a better thing to call something, we should call it that.
If the suggestion of making this type of change (with the added reasoning of being sensitive and empathetic towards other folks in your professional community) lights a fire in your belly or upsets you, then there's a bigger, personal, problem at hand.
Ditto what @ben said.
I think as software developers we're notoriously bad at naming things, and this particular terminology falls firmly under the umbrella of "bad names for things".
The insistence of folks to cleave to (and argue for) these outdated and poorly chosen names is foolish, regardless of the reason.
If there's a better thing to call something, we should call it that.
If the suggestion of making this type of change (with the added reasoning of being sensitive and empathetic towards other folks in your professional community) lights a fire in your belly or upsets you, then there's a bigger, personal, problem at hand.
For some comic relief, I'm reminded of this:
Bullfrog? I'd have called it a Chazwazza!
