Well, yes, I am convinced it's the correct decision, and by extension I do believe that people who disagree are at best misguided, and at worst are actively invested in perpetuating systemic inequality.

I'll agree that git's use of "master" is not as egregious as "master/slave" in database terminology, but it's still not great.

There are two prevailing uses of the term "master". One refers to the quality of being exceptionally good at a particular skill. By and large, I don't think most people have a problem uses of "master" where that's the intended meaning. But "master" in the sense of "leader" or "controlling" isn't great, even if (in the case of git's "master" naming) there isn't a corresponding "slave" role.

> if you try to point this out and discuss it at a company like Github (or mine) where the group making these decisions is convinced of their correctness you risk ostracization and career suicide

I agree that this is bad. These sorts of responses have a chilling effect on reasonable conversations and discussion. But in some ways I do understand why this happens; people who are directly affected by terminology like this are getting really tired of having the same conversations over and over about something that evokes significant emotional pain every time it's brought up. Again, it's not great, but I think it's understandable. And it's frankly hard to understand why using a word like "master" in technical terminology is somehow so important that it's even worth getting into repetitive discussion after discussion about it, especially when doing so causes some people pain. That's where the concerns about empathy and compassion come into play, because the people who constantly fight against this change do not seem to be even trying to look at this from someone else's point of view. (And I say this as someone who initially was resistant to these changes, but have since realized that I was wrong to do so.)