Linux 5.8 Formally Adds the Inclusive Terminology Guidelines
In an effort to make this thread more interesting:<p>I think we should get used to the idea of just letting stuff like this happen. What&#x27;s the downside? Is it <i>really</i> so hard to type &quot;main&quot; instead of &quot;master&quot;?<p>I get the argument that historically, language has been used to control populations, and therefore it&#x27;s good to resist attempts to control language. But every time someone complains about master vs main, I can&#x27;t help but think thoughts that would be rude to repeat.<p>I recently made a tool for managing TPUs, called tpunicorn (tpudiepie was &quot;clever, but risks legal issues&quot;): <a href="https:&#x2F;&#x2F;github.com&#x2F;shawwn&#x2F;tpudiepie" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;shawwn&#x2F;tpudiepie</a><p>The tool lists a bunch of info about the TPUs, including their master IP address. It&#x27;s the IP of host 0, in charge of TPU configuration.<p>If someone were to open an issue &quot;Please change master to main,&quot; and they were genuine about the request, I&#x27;d be like ... ok. And that would be the end of it. It&#x27;s a s&#x2F;master&#x2F;main&#x2F;g. Sure, whatever.<p>So, my question for you, dear readers: why <i>not</i> just say ok and be done with it? Is the spirit of rebellion really so ingrained in everyone that this is the battle we want to fight? You can mock it, ridicule it, fight it, but ultimately it&#x27;s a big bikeshed that people want to paint. Why not let them?<p>And, you know, maybe it might help. A female dev I know recently expressed frustration about being called a &quot;guy&quot; constnatly. &quot;Hey guys, ...&quot; It&#x27;s why I say ya&#x27;ll. She also feels bad about mentioning it, because she doesn&#x27;t want to be an imposition.<p>From my point of view, this is a big ball of &quot;whatever, who cares, just do it.&quot; But my mind is open: can you convince me that it&#x27;s important to resist this trend? Without invoking slippery-slope arguments?