<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Change of computing terms?</title>
	<atom:link href="http://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Mon, 13 Apr 2026 10:12:12 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1711085</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 18 May 2021 20:46:35 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1711085</guid>
		<description><![CDATA[What.... We can no longer use a male and female to plug the master into the slave anymore??]]></description>
		<content:encoded><![CDATA[<p>What&#8230;. We can no longer use a male and female to plug the master into the slave anymore??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1692917</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sat, 26 Sep 2020 05:37:41 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1692917</guid>
		<description><![CDATA[Human Capital: Moving away from &#039;master/slave&#039; terminology
https://tcrn.ch/30beHq1

This week, we&#039;re looking at the use of &quot;master/slave&quot; terminology in computer programming and the current state of gig workers in California.]]></description>
		<content:encoded><![CDATA[<p>Human Capital: Moving away from &#8216;master/slave&#8217; terminology<br />
<a href="https://tcrn.ch/30beHq1" rel="nofollow">https://tcrn.ch/30beHq1</a></p>
<p>This week, we&#8217;re looking at the use of &#8220;master/slave&#8221; terminology in computer programming and the current state of gig workers in California.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1692099</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 21 Sep 2020 06:42:52 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1692099</guid>
		<description><![CDATA[Catalin Cimpanu / ZDNet: 	
Starting Oct. 1, all new source code repositories on GitHub will be named “main” instead of “master” as part of company&#039;s effort to abandon non-inclusive terms  —  All new Git repositories on GitHub will be named “main” instead of “master” starting October 1, 2020.
https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/]]></description>
		<content:encoded><![CDATA[<p>Catalin Cimpanu / ZDNet:<br />
Starting Oct. 1, all new source code repositories on GitHub will be named “main” instead of “master” as part of company&#8217;s effort to abandon non-inclusive terms  —  All new Git repositories on GitHub will be named “main” instead of “master” starting October 1, 2020.<br />
<a href="https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/" rel="nofollow">https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1685914</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 21 Jul 2020 20:23:09 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1685914</guid>
		<description><![CDATA[Linux Sound Subsystem Begins Cleaning Up Its Terminology To Meet Inclusive Guidelines
https://www.phoronix.com/scan.php?page=news_item&amp;px=Linux-ALSA-Inclusive-Terms&amp;lol]]></description>
		<content:encoded><![CDATA[<p>Linux Sound Subsystem Begins Cleaning Up Its Terminology To Meet Inclusive Guidelines<br />
<a href="https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-ALSA-Inclusive-Terms&#038;lol" rel="nofollow">https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-ALSA-Inclusive-Terms&#038;lol</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1685913</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 21 Jul 2020 20:22:12 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1685913</guid>
		<description><![CDATA[Merged just over one week ago to the mainline kernel were [inclusive terminology guidelines](https://www.phoronix.com/scan.php?page=news_item&amp;px=Linux-5.8-Inclusive-Terminology) following [the recent discussion among upstream developers](https://www.phoronix.com/scan.php?page=news_item&amp;px=Linux-Inclusive-Terminology). The Linux sound subsystem has begun preparing patches for Linux 5.9 to overhaul their naming conventions as a result.]]></description>
		<content:encoded><![CDATA[<p>Merged just over one week ago to the mainline kernel were [inclusive terminology guidelines](<a href="https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-5.8-Inclusive-Terminology" rel="nofollow">https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-5.8-Inclusive-Terminology</a>) following [the recent discussion among upstream developers](<a href="https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-Inclusive-Terminology" rel="nofollow">https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-Inclusive-Terminology</a>). The Linux sound subsystem has begun preparing patches for Linux 5.9 to overhaul their naming conventions as a result.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1685339</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Thu, 16 Jul 2020 17:15:33 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1685339</guid>
		<description><![CDATA[https://www.theregister.com/2020/07/13/linux_adopts_inclusive_language/]]></description>
		<content:encoded><![CDATA[<p><a href="https://www.theregister.com/2020/07/13/linux_adopts_inclusive_language/" rel="nofollow">https://www.theregister.com/2020/07/13/linux_adopts_inclusive_language/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1685022</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sun, 12 Jul 2020 07:30:36 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1685022</guid>
		<description><![CDATA[Linux team approves new terminology, bans terms like &#039;blacklist&#039; and &#039;slave&#039;
https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/

Linux creator Linus Torvalds puts stamp on proposal to use neutral language in kernel code and documentation.

Proposed alternatives for master/slave include:

primary/secondary
main/replica or subordinate
initiator/target
requester/responder
controller/device
host/worker or proxy
leader/follower
director/performer

Proposed alternatives for blacklist/whitelist include:

denylist/allowlist
blocklist/passlist

The Linux team did not recommend any specific terms but asked developers to choose as appropriate.]]></description>
		<content:encoded><![CDATA[<p>Linux team approves new terminology, bans terms like &#8216;blacklist&#8217; and &#8216;slave&#8217;<br />
<a href="https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/" rel="nofollow">https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/</a></p>
<p>Linux creator Linus Torvalds puts stamp on proposal to use neutral language in kernel code and documentation.</p>
<p>Proposed alternatives for master/slave include:</p>
<p>primary/secondary<br />
main/replica or subordinate<br />
initiator/target<br />
requester/responder<br />
controller/device<br />
host/worker or proxy<br />
leader/follower<br />
director/performer</p>
<p>Proposed alternatives for blacklist/whitelist include:</p>
<p>denylist/allowlist<br />
blocklist/passlist</p>
<p>The Linux team did not recommend any specific terms but asked developers to choose as appropriate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1685021</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sun, 12 Jul 2020 07:26:42 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1685021</guid>
		<description><![CDATA[It’s Time for IEEE to Retire ‘Master / Slave&#039;
https://www.eetimes.com/its-time-for-ieee-to-retire-master-slave/?utm_content=buffer92bef&amp;utm_medium=social&amp;utm_source=edn_facebook&amp;utm_campaign=buffer]]></description>
		<content:encoded><![CDATA[<p>It’s Time for IEEE to Retire ‘Master / Slave&#8217;<br />
<a href="https://www.eetimes.com/its-time-for-ieee-to-retire-master-slave/?utm_content=buffer92bef&#038;utm_medium=social&#038;utm_source=edn_facebook&#038;utm_campaign=buffer" rel="nofollow">https://www.eetimes.com/its-time-for-ieee-to-retire-master-slave/?utm_content=buffer92bef&#038;utm_medium=social&#038;utm_source=edn_facebook&#038;utm_campaign=buffer</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1684462</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Mon, 06 Jul 2020 05:04:40 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1684462</guid>
		<description><![CDATA[Infosec community disagrees with changing &#039;black hat&#039; term due to racial stereotyping
https://www.zdnet.com/article/infosec-community-disagrees-with-changing-black-hat-term-due-to-racial-stereotyping/

A Google security researcher withdrew from the Black Hat security conference and asked the community to stop using the &#039;black hat&#039; term.

The information security (infosec) community has angrily reacted today to calls to abandon the use of the &#039;black hat&#039; and &#039;white hat&#039; terms, citing that the two, and especially &#039;black hat,&#039; have nothing to do with racial stereotyping.

Discussions about the topic started late last night after David Kleidermacher, VP of Engineering at Google, and in charge of Android Security and the Google Play Store, withdrew from a scheduled talk he was set to give in August at the Black Hat USA 2020 security conference.

In his withdrawal announcement, Kleidermacher asked the infosec industry to consider replacing terms like black hat, white hat, and man-in-the-middle with neutral alternatives.

While a part of the infosec community agreed with Kledermacher, the vast majority did not, and called it virtue signaling taken to the extreme.

Most security researchers pointed to the fact that the terms had nothing to do with racism or skin color, and had their origins in classic western movies, where the villain usually wore a black hat, while the good guy wore a white hat.

Others pointed to the dualism between black and white as representing evil and good, concepts that have been around since the dawn of civilizations, long before racial divides even existed between humans.

Companies like Twitter, GitHub, Microsoft, LinkedIn, Google, Ansible, and others committed to changing technical language in their products and infrastructure to remove terms like master, slave, blacklist, whitelist, and others.

But these efforts to move away from offensive terms like master, slave, blacklist, whitelist started even before the Black Lives Matter protests.

Companies and open-source projects like Drupal, Python, PostgreSQL, and Redis had removed offensive terms years before, some as early as the late 2000s.

In May 2020, even the UK government&#039;s cyber-security agency, the NCSC, announced it would stop using &quot;whitelist&quot; and &quot;blacklist&quot; due to stigma and racial stereotyping surrounding the two terms.

The trend of cleaning tech language was well underway, but the Black Lives Matter protests gave it a boost and helped it gain mainstream media attention and more backing.

However, the infosec community is not willing to accept change at this moment for terms it doesn&#039;t see as offensive, and chances are the terms are here to stay.]]></description>
		<content:encoded><![CDATA[<p>Infosec community disagrees with changing &#8216;black hat&#8217; term due to racial stereotyping<br />
<a href="https://www.zdnet.com/article/infosec-community-disagrees-with-changing-black-hat-term-due-to-racial-stereotyping/" rel="nofollow">https://www.zdnet.com/article/infosec-community-disagrees-with-changing-black-hat-term-due-to-racial-stereotyping/</a></p>
<p>A Google security researcher withdrew from the Black Hat security conference and asked the community to stop using the &#8216;black hat&#8217; term.</p>
<p>The information security (infosec) community has angrily reacted today to calls to abandon the use of the &#8216;black hat&#8217; and &#8216;white hat&#8217; terms, citing that the two, and especially &#8216;black hat,&#8217; have nothing to do with racial stereotyping.</p>
<p>Discussions about the topic started late last night after David Kleidermacher, VP of Engineering at Google, and in charge of Android Security and the Google Play Store, withdrew from a scheduled talk he was set to give in August at the Black Hat USA 2020 security conference.</p>
<p>In his withdrawal announcement, Kleidermacher asked the infosec industry to consider replacing terms like black hat, white hat, and man-in-the-middle with neutral alternatives.</p>
<p>While a part of the infosec community agreed with Kledermacher, the vast majority did not, and called it virtue signaling taken to the extreme.</p>
<p>Most security researchers pointed to the fact that the terms had nothing to do with racism or skin color, and had their origins in classic western movies, where the villain usually wore a black hat, while the good guy wore a white hat.</p>
<p>Others pointed to the dualism between black and white as representing evil and good, concepts that have been around since the dawn of civilizations, long before racial divides even existed between humans.</p>
<p>Companies like Twitter, GitHub, Microsoft, LinkedIn, Google, Ansible, and others committed to changing technical language in their products and infrastructure to remove terms like master, slave, blacklist, whitelist, and others.</p>
<p>But these efforts to move away from offensive terms like master, slave, blacklist, whitelist started even before the Black Lives Matter protests.</p>
<p>Companies and open-source projects like Drupal, Python, PostgreSQL, and Redis had removed offensive terms years before, some as early as the late 2000s.</p>
<p>In May 2020, even the UK government&#8217;s cyber-security agency, the NCSC, announced it would stop using &#8220;whitelist&#8221; and &#8220;blacklist&#8221; due to stigma and racial stereotyping surrounding the two terms.</p>
<p>The trend of cleaning tech language was well underway, but the Black Lives Matter protests gave it a boost and helped it gain mainstream media attention and more backing.</p>
<p>However, the infosec community is not willing to accept change at this moment for terms it doesn&#8217;t see as offensive, and chances are the terms are here to stay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2020/06/16/change-of-computing-terms/comment-page-1/#comment-1684452</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Sun, 05 Jul 2020 21:19:29 +0000</pubDate>
		<guid isPermaLink="false">https://www.epanorama.net/blog/?p=186429#comment-1684452</guid>
		<description><![CDATA[&quot;These new guidelines for Linux kernel developers call for initially avoiding words including &quot;slave&quot; and &quot;blacklist&quot; to instead use words like subordinate, replica, follower, performer, blocklist, or denylist. &quot;

Nerds gonna be big mad

https://www.phoronix.com/scan.php?page=news_item&amp;px=Linux-Inclusive-Terminology]]></description>
		<content:encoded><![CDATA[<p>&#8220;These new guidelines for Linux kernel developers call for initially avoiding words including &#8220;slave&#8221; and &#8220;blacklist&#8221; to instead use words like subordinate, replica, follower, performer, blocklist, or denylist. &#8221;</p>
<p>Nerds gonna be big mad</p>
<p><a href="https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-Inclusive-Terminology" rel="nofollow">https://www.phoronix.com/scan.php?page=news_item&#038;px=Linux-Inclusive-Terminology</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
