Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't understand why there was such manufactured outrage over master branches, but not master recordings.


The terms are from different industries with different visibility.

When this became a social moment, there was a sentiment that everybody should learn to code and lots of people were being exposed to things like git, and having casual discussions about those things on social media, at meetups, etc.

It went from being an professional engineer's tool to part of a pop culture zeitgeist, where everybody could share some opinion about it.

While many people know what a "master recording" is when the phrase comes up, the number of people actively thinking about and discussing audio/studio engineering remains way smaller and has way less intersection with communities compelled to make noise about language politics.


I think the idea that there was outrage about branch naming is manufactured.

It was more that the naming was potentially offensive and cost next to nothing to change.

The people griping about it are the ones outraged.


Potentially offensive in what way?


There was outrage to be had and those who revel in it pounced.


Or databases and harddisk redundancy configurations. Or Zen masters. Or masterclass. Or a master's degree. Or mastermind.

We should get rid of all these words right?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: