3 ms·
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 n
by WalterGR 5y ago
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 https://news.ycombinator.com/item?id=26487854
Presumably breakage was anticipated back then?
What does this add?
- draw_down 5y ago
- bewaretheirs 5y agoIt shows ongoing impact rather than a one-time cost from an incompatible change.
- WalterGR 5y agoFor 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.
- drewcoo 5y agoOr 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.