I think the argument that calling git branches "master" hurts people is ridiculous, but I also think that "main" makes more sense. The master/main branch doesn't have any power over other branches - it's just the one that you happen to use primarily. "Main" describes that better.
I sometimes regret having built up tons of Bash aliases, because in the long term it ends up with me not really knowing half the tools I use, just my little cryptic vocabulary.
In my view, it’s a bit more nuanced. In modern development at companies, most of the time trunk-based version management is used and having it called “main” makes sense, but earlier, when got was one of the few VCSs out there for open source development, I think master may have conveyed a different meaning. Generally, with the highly-distributed nature of systems like Linux, you need to know which remote and branch the version you are updating or referencing was mastered in for the remote you are submitting a patch to, for example. I think of it as coming from the term master copy—not because it has power over other branches but because it’s the canonical authoritative source for that remote.
Sure it is better. But changing things comes with a cost. Tons of git tooling which could previously just ASSUME master was the primary branch must now figure out what the branch is, instead.
The amount of time people have spent on this change fixing broken tools and workflows makes it a stupid change all by itself.
I note that "master (verb)" is on the list, but "mastery" is not.
So apparently a Stanford M.S., M.A. or M.F.A. degree may be said to denote mastery of a subject, but its holder cannot claim to have mastered the subject. So many ways to get it wrong...
But git branch names now say "main".