"Road to hell is paved with good intentions" is what I think.
What will this change for people of color? Everybody will have to use new term they are not used to. This only creates more unnecessary work for creators.
I love good coffee, meaning strong, dark espresso! Regular Expressions are like word-puzzles to me, as are LINQ queries. I take pictures everywhere I go. Husband of 1, father of 2.
The fact that it is causing a lot of people a small frustration may also get them to think. I've seen a lot of discussions happening on why these terms are bad. Even if people were to completely leave their branches alone, they may have learned something.
The master branch in Git was just a placeholder name anyway. With repos forking there is no real concept of master. Or, as the Pro Git book often calls it the 'blessed master', which, in hindsight, sounds even worse.
Developer advocate, full-stack engineer, startup co-founder & CTO, bringing 15 years of experience in Silicon Valley, including at Google and Yahoo!. Public speaker.
Location
🌐
Education
UC Santa Cruz Extension
Work
Developer Advocate at Weaviate, the open-source semantic search engine
I love good coffee, meaning strong, dark espresso! Regular Expressions are like word-puzzles to me, as are LINQ queries. I take pictures everywhere I go. Husband of 1, father of 2.
I'm guessing it won't be as horrible as painted. Plus, you don't have to change. It's entirely optional. It's not that there will be a blocklist of bad branch names built into every git command line...
And there are safer ways to do this than just renaming everything. Adding a little automation to make main mirror master, update the builds over time, add hooks to warn users etc.
It will be far less painful as we adopt ways to more easily resolve these problems.
The small frustrations I was alluding to were the small open source projects and personal Repos that can change easily. I was done in less than 2 hours. But maybe some of my forks may need to spend some time too. And maybe some links from blogs and stackoverflow will break. For me, that's ok.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Road to hell is paved with good intentions" is what I think.
What will this change for people of color? Everybody will have to use new term they are not used to. This only creates more unnecessary work for creators.
The fact that it is causing a lot of people a small frustration may also get them to think. I've seen a lot of discussions happening on why these terms are bad. Even if people were to completely leave their branches alone, they may have learned something.
The master branch in Git was just a placeholder name anyway. With repos forking there is no real concept of master. Or, as the Pro Git book often calls it the 'blessed master', which, in hindsight, sounds even worse.
Renaming "master" will be no small frustration.
I'm guessing it won't be as horrible as painted. Plus, you don't have to change. It's entirely optional. It's not that there will be a blocklist of bad branch names built into every git command line...
And there are safer ways to do this than just renaming everything. Adding a little automation to make main mirror master, update the builds over time, add hooks to warn users etc.
It will be far less painful as we adopt ways to more easily resolve these problems.
The small frustrations I was alluding to were the small open source projects and personal Repos that can change easily. I was done in less than 2 hours. But maybe some of my forks may need to spend some time too. And maybe some links from blogs and stackoverflow will break. For me, that's ok.