3 ms·
If you strip away all the political outrage what’s actually happening on a technical level is that git is adding a new feature: customisable default branches. I
by afavour 6y ago
If you strip away all the political outrage what’s actually happening on a technical level is that git is adding a new feature: customisable default branches. I imagine they will provide an option to use it (“git checkout —-default” or whatever) and yes, you’ll have to update your tests to accommodate it. I’ve lost count of the number of times I’ve had to tweak code because of an external API change that doesn’t benefit me personally. Often it involves using an entire new API because the old one is being retired! Compared to that this is a walk in the park. A couple of hours at most. And yet everyone is expending hours upon hours arguing about it.
- IshKebab 6y agoRight but people are arguing about it because it is unnecessary! I bet if an API you use broke backwards compatibility just so it could `color` to `colour` you'd be arguing against it too!
- afavour 6y agoOK so we’re finally at the actual core of the matter: the technical arguments aren’t actually valid, it’s that you don’t think it’s worth the minimal effort because you don’t personally know of anyone that is offended by the master/slave connotation of “master” branches. That’s always the actual core of the complaint yet everyone dances around it.
- fuzxi 6y agoHe didn't dance around it; it was the first thing he said. https://news.ycombinator.com/item?id=26455182 https://news.ycombinator.com/item?id=26455182