Well 'main' is a more intuitive & UX friendly name than 'master' which new devs are going to intuitively relate to as it's commonly used to refer to the 'main thing', e.g. main road, main course, etc. I can't recall the last time I used 'Master' as a synonym to 'main' outside of technology (as a Redis Client author I still deal with Master nomenclature a bit). Can only think of 'Masters degree' but that has to do wit…
I disagree. "Master" is a pre-existing term closer to the actual meaning of that branch in a repository the way most developers work. Cambridge https://dictionary.cambridge.org/us/dictionary/english/maste... : an original version of something from which copies can be made Merriam Webster https://www.merriam-webster.com/dictionary/master : being a device or mechanism that controls the operation of another mechanism or…
But I don't believe "Master" is more intuitive nomenclature for new devs learning version control either nor a better representation for the naming the main branch where terminology is around a tree with branches being created from and committed to the 'main' single branch (i.e. trunk). When visualizing branches in a commit history it's shown and referred to as branches off the main trunk that deviates from the main branch at different commit points that may or may not return to the main branch like small roads off a main highway. The emphasis of branches being they're deviations or snapshots of a main branch's commit timeline, not in their state in which they're old copies of a main branch. The "Master copy" by definition does not change, it's a completed artwork, which is the opposite in CVS where it's always growing & changing with a tree of commits and often it's the branches which are snapshots of the main branch in labelled, well-defined points in its history.
Either way the terminology is definitely moving away usage of 'master' in new Software, so I don't fault their reasoning for deprecating existing naming and moving to more modern, intuitive & inclusive terminology.