It’s shorter. Also “master” is especially egregious as as it requires the last 5 letters to be typed with the same hand, while “main” makes better use of bimanual parallelism.
European here. I’m a supporter of civil rights and against racism and so on, but that controversy with master vs main for me is just a silly us american controversy, as master has more meanings that just owner of a slave (and in this context, it’s not even related to that master-slave thing as used to be in hardware naming).
The issue is that kind of (in my pov, unnecessary) change caused an outage in my company as some k8s objects changed its label because of this kind of controversy, and some of our selectors were not ready for that change, as iirc this happened in a minor version upgrade. We also had to invest development hours to update internal tooling to support that change too (and I bet, a lot of companies did the same).
Agree with this. Never changed from master as it would cost the business money to do so (and involve a ton of headaches) for no reason. Thankfully the whole dept agreed on that.
I’m glad I’m not part of “we”
Why do you care
Because this whole discussion is fucking stupid. There was no good reason for a change.
I like the actual look of the word “main” more than I do the word “master”. I think it’s because it looks like a neat semi-circle
It also makes more sense.
It’s shorter. Also “master” is especially egregious as as it requires the last 5 letters to be typed with the same hand, while “main” makes better use of bimanual parallelism.
The good reason was that it bothered some people. “Main” is two fewer letters, so it’s even more convenient to type. So what’s the problem?
European here. I’m a supporter of civil rights and against racism and so on, but that controversy with master vs main for me is just a silly us american controversy, as master has more meanings that just owner of a slave (and in this context, it’s not even related to that master-slave thing as used to be in hardware naming).
The issue is that kind of (in my pov, unnecessary) change caused an outage in my company as some k8s objects changed its label because of this kind of controversy, and some of our selectors were not ready for that change, as iirc this happened in a minor version upgrade. We also had to invest development hours to update internal tooling to support that change too (and I bet, a lot of companies did the same).
Agree with this. Never changed from master as it would cost the business money to do so (and involve a ton of headaches) for no reason. Thankfully the whole dept agreed on that.