|
|
|
|
|
by oji0hub
1921 days ago
|
|
> Now a group of people has proposed a different convention that they like better, Umm, no, they were pressured into it. That also means the reason they're doing it is pressure, not liking it. > and it's gained traction. It didn't "gain" traction. It was forced on people by various means of pressure. |
|
"They": who do you mean by this? Do you mean every group of engineers who has made the change? Just GitHub? The Software Conservancy?
"Not liking it": I suppose you have evidence that these changes were generally unsatisfactory to the people making them? And not, say, you projecting your own anger upon them?
"Pressure": You seem by this to posit that conventions ought not to act by pressure at all, which is a really weird way to imagine how the world works. How could a convention, or a change in convention, _not_ generate pressure?
"Forcing": You seem determined to strip engineers of their own agency, but this is silly. Only defaults have changed. Master branches still abound, and renaming within Git itself remains a relatively trivial matter.
"Gain traction": You have not been paying attention if you think this terminology shift was a sudden change made all at once from the top down. I've been in debates about master/slave terminology in CS (and specifically Git) going back to Ferguson, maybe even longer.
I get that you like your old branch name and you don't want the hassle of changing it, but all this talk of "pressure" and "forcing" by nameless adversaries is quite unnecessary to get that point across.