News for hackers. Stuff that matters.

A comment on Could we please get back the master-branch on this repository?.

Re:Could we please get back the master-branch on this reposi... by WalterGR on Wednesday February 09, 2022 @12:23PM (#30275264)
Is this interesting for any reason beyond the obvious culture war one? This is the 6th highest-ranking submission over the past 12 months:

GitHub, fuck your name change (mooseyanon.medium.com)

3353 points by leontrolski | 10 months ago | 2084 comments

https://news.ycombinator.com/item?id=26487854

Presumably breakage was anticipated back then?

What does this add?

[ Parent | on HN ]
Re:Could we please get back the master-branch on this reposi... by bewaretheirs on Wednesday February 09, 2022 @12:57PM (#30275766)
It shows ongoing impact rather than a one-time cost from an incompatible change.
[ Parent | on HN ]
Re:Could we please get back the master-branch on this reposi... by WalterGR on Wednesday February 09, 2022 @01:16PM (#30276049)
For one team? at one org who didn’t keep their stuff up-to-date regarding one project.

A collection of tickets such as this one plus some analysis? Could be interesting. But this is just noise.

Edit: To be interesting, that analysis would have to compare with other kinds of breaking changes that happen in software constantly.

[ Parent | on HN ]
Re:Could we please get back the master-branch on this reposi... by drewcoo on Wednesday February 09, 2022 @02:29PM (#30277248)
Or does the exception prove the rule?

The fact that this is the only instance of problems says that the change effectively caused no ongoing problems.

[ Parent | on HN ]