main(n.)
Old English mægen (Mercian megen) "power, bodily strength; force, violent effort; strength of mind or will; efficacy; supernatural power," from Proto-Germanic *maginam "power" (source also of Old High German megin "strength, power, ability"), reconstructed to be from a suffixed form of PIE root *magh- "to be able, have power."
The original sense of "power" is preserved in phrase might and main. Also used in Middle English for "royal power or authority" (c. 1400), "military strength" (c. 1300), "application of force" (c. 1300).
I really really wish the ecosystem had simply gone with "trunk" (which is also what Subversion had used, in addition to actually matching the metaphor in play; though, I get that some people don't consider trunk to be a branch... but it is already used in this context for "trunk-based development").
Outside of the context of the culture war, it has gotten a project or two that I've seen to really think about what they should name their branches, and how they could better describe what kind of development happens in them.
Branch names like "stable", "next", and "protobreak" are a lot more understandable than "master" or even "main."
I'm curious what kinds of problems took dozens of hours to fix. We had a script that was using master, and the default name of main (Github) broke things. But it wasn't a surprise, we knew it was coming, someone just forgot to adjust a script.
They just changed the script, took about 30 seconds. If you had a lot of scripts, then you could always make a master branch and use it instead of main. That would also be pretty quick to fix.
And it wasn't like when Github changed things (or now git itself will be changing) there weren't announcements. You'd have to have been living under a rock to not know about it and be taken by surprise.
One of the companies I worked for had self-hosted subversion hosting and accessing it required connecting to a VPN first. The IP address of that SVN server changed multiple times as we migrated between hardware and even VPN providers.
It's annoying, but you just dig up the new credentials, update the script to point to the right place and move on with your life. I shudder to think of the kind of environment where updating a branch name... not even a domain or IP address... would cause significant turmoil.
not your parent commenter and I have yet to have a problem with the branch name change but I could see it taking a long time to figure out. It's perfectly normal to assume branch names don't change often, specially master/main.
Abd if it took Cloudflare 3 hours to find out that a rust process was panicing and crashing, a branch name change in someone's ci/cd is less expected in the chain of probable causes and could take more time to detect.
The terms are from different industries with different visibility.
When this became a social moment, there was a sentiment that everybody should learn to code and lots of people were being exposed to things like git, and having casual discussions about those things on social media, at meetups, etc.
It went from being an professional engineer's tool to part of a pop culture zeitgeist, where everybody could share some opinion about it.
While many people know what a "master recording" is when the phrase comes up, the number of people actively thinking about and discussing audio/studio engineering remains way smaller and has way less intersection with communities compelled to make noise about language politics.
It's the novlang of 1984. Its shows were our society is headed, slowly but surely.
Little bit little remove or ban the language that might be offensive to some. Twist the meaning of things to ensure that normal words become "shameful" words when used. Until people forget. Then you can reach this society were there is no contestation, no social agitation and political unrest because the concept doesn't even exist.
Same here. The first time I heard 'main' as a replacement name for master, I immediately used it everywhere. Easier to say for me, easier to type for me. I find the societal discussion around is absurd. But I couldn't also care less.
A little bit... a lot of people already made the switch, and a lot of people start new repos via github/gitlab instead of local anyway. I feel the argument itself is somewhat silly to begin with.
I thought this nonsense was about to go away noticed even github starting to default to master or maybe it was the terminal git. Sensoring tech words about things that happened 300 years ago is not OK
Saying a word is bad is pretty much the definition of censorship yes. Not the context it is used, not the implications when it is used but uncategorically BAD - it just breaks my somewhat autistic brain on the principle.
PS: I have an african wife and let me tell you she has no beef with the word, she will have more beef with me talking to the cashier in a way that is too friendly
This seems like a you problem. I have quite a few repos made before using "main" was the default in GitHub or Git. I have not changed them, and I have never spent more than 5 seconds thinking about it, let alone worrying about being considered "less of a person" because of it.
In the spirit of genuine curiosity, who is making you feel like less of a person wrt the choice of main/master, and how are they doing that?
It sounds like you're saying that git maintainers are intending for you to feel like less of a person because you don't agree with their choice, but I don't understand how you arrived at that conclusion.
> Saying a word is bad is pretty much the definition of censorship yes. Not the context it is used, not the implications when it is used but uncategorically BAD
No expressing an opinion, eve ln an unqualified unconditional one, about a word is not the fee definition of censorship. Forcing others not to publish what you don't like is censorship (even if that dislike is based in context and conditions, and not unconditional opposition to a word.) Presenting an opinion is just presenting an opinion.
> it just breaks my somewhat autistic brain on the principle.
Yeah, you not liking an opinion doesn’t convert that opinion into censorship, either.
