If you're going to convince me that you're "anti-woke" suggestions are better than the "woke" suggestions that got us here in the first place, do so in the traditional way. Make an argument for why moving back to master makes substantive improvements in my workflow as a developer and not because you find it aesthetically concerning. And why it is financially beneficial for the globe to spend the engineer-years it would take to make this change.
Also, I don't know that I'm convinced that 'master' in this scenario is more descriptive than 'main'.
This is sort of the inverse of the sunk cost fallacy. We are where we are, if we want to move back, it's not implicitly rational to move back solely for the opposite reason that we moved forward.
Moving back has additional costs, it doesn't simply undo the costs of moving forward.
Comments
If you're going to convince me that you're "anti-woke" suggestions are better than the "woke" suggestions that got us here in the first place, do so in the traditional way. Make an argument for why moving back to master makes substantive improvements in my workflow as a developer and not because you find it aesthetically concerning. And why it is financially beneficial for the globe to spend the engineer-years it would take to make this change.
Also, I don't know that I'm convinced that 'master' in this scenario is more descriptive than 'main'.
The change originally was never about developer experience.
This is sort of the inverse of the sunk cost fallacy. We are where we are, if we want to move back, it's not implicitly rational to move back solely for the opposite reason that we moved forward.
Moving back has additional costs, it doesn't simply undo the costs of moving forward.