okay so as much as people like to meme on the whole banning blacklist/whitelist thing, it actually makes things clearer to just say blocklist/allowlist, especially for non-native speakers.
People got grumpy about master/slave being replaced with server/client, superior/subordinate, leader/follower, and similar terms but that actually largely benefits as well in that it makes things clearer. Anyone who has dealt with bus protocols that support the more complex "multi-leader" setups or peer-to-peer setups knows how the master/slave terminology can be confusing and potentially limiting in accurately describing the parts of the system.
And the git master/main thing also is more a matter of just making things easier to pick up. Master can be confusing there for the same reasons it's confusing in bus topologies. Main instead is obvious. It's the main/mainline branch of the project. And that also helps set the divide for main vs feature vs maintenance branches (and release tags).
So yeah some of it was done under the guise of politics but that's generally been more about getting an excuse to make the change without people dismissing it rather than the underlying reason for the change to happen.
I tend to not really notice whtever slight cleanliness/communication improvement any of these changes add (this is probably just a me thing).
So, putting politics aside, I don't really care as long as it isn't breaking existing stuff. My only point of contention has been the politics behind some of the pushes.
People got grumpy about master/slave being replaced with server/client, superior/subordinate, leader/follower, and similar terms but that actually largely benefits as well in that it makes things clearer. Anyone who has dealt with bus protocols that support the more complex "multi-leader" setups or peer-to-peer setups knows how the master/slave terminology can be confusing and potentially limiting in accurately describing the parts of the system.
And the git master/main thing also is more a matter of just making things easier to pick up. Master can be confusing there for the same reasons it's confusing in bus topologies. Main instead is obvious. It's the main/mainline branch of the project. And that also helps set the divide for main vs feature vs maintenance branches (and release tags).
So yeah some of it was done under the guise of politics but that's generally been more about getting an excuse to make the change without people dismissing it rather than the underlying reason for the change to happen.