You'll quickly stop being surprised on this one because this change is inevitable across the industry in the coming years. I too had the same reaction when I was first exposed to the change a year ago, but now I'm "meh" about it. Language evolves a lot over time, surprisingly quickly. And allowlist/denylist really are better words to describe what's going on, even ignoring the other connotations.
Another similar change that's rapidly approaching is renaming the master branch to main (which, again, seems like a superior choice to me even divorced from the larger cultural context).
RuboCop is probably a trademark violation. I wouldn't have known it was a linter without another post in here mentioning a fork that changes the name. It's the first result on Google for "ruby linter," but it's half a page down on DuckDuckGo.
I didn't really have a problem with "master," but it does seem like it tracks back to master/slave tapes based on a mailing list post, and there are clearer terms to use.
And so on. If people are going to call to arms over a name or term, can it at least be one worth defending? For an industry that worships at the altar of Move Fast And Break Things, some people get extremely conservative about strings of glyphs.
Good point about GIMP. That always was a terrible name. Sometimes we coders are too "clever" for our own good and need someone who knows about branding to rein us in.
It'd be one thing if these changes weren't improvements, but they are, and opposing them solely because someone you perceive to be an "SJW" is proposing them is overly reactionary.
[1] https://github.com/rails/rails/pull/33681