Nice examples. On one hand, once etymology of a word is old enough, it becomes forgotten and not many people are offended; on the other hand, once that etymolog

Nice examples. On one hand, once etymology of a word is old enough, it becomes forgotten and not many people are offended; on the other hand, once that etymology is brought to light, continuing to use that word may become an ethically questionable choice. That said, the pushback against “master” and “blacklist” seems related not to etymology (origins of those words don’t involve race or slavery) but to connotations acquired afterwards. > We should listen to each other more and if these terms are a barrier then there really is no harm to using other terms. Agreed. I’m personally torn on this issue. On one hand, the fact that these words rub people wrong is an indicator of a deeper problem—in an ideal world, no one would take a term personally because they’d know it denotes a technical concept and isn’t intended to put anyone down; on the other hand, it’s not really that difficult to stop using some terms in new codebases. On one hand, we should get input from those directly affected by this; on the other hand, those affected may choose to stay silent despite possible discomfort and treat it as a problem with their insecurities rather than the industry.