←back to thread

Avoid master/slave terminology

(bugs.python.org)
34 points atoledano | 1 comments | 10 Sep 18 20:15 UTC | HN request time: 0.213s | source
Show context
badrabbit ◴[10 Sep 18 21:23 UTC] No.17955320[source]▶
No problem against this,good if it makes anyone more comfortable in the community.

Master/slave relationship is not uncommon throught history. I think if someone learned history well this wouldn't offend them all that much. But still,this isn't a misunderstanding worth making anyone uncomfortable. When I was a teenager,I remember similarly feeling uncomfortable with IDE interface's master/slave terminology.

replies(3): >>17955500 #>>17956040 #>>17956044 #
1. rtpg ◴[10 Sep 18 23:37 UTC] No.17956040[source]▶
Not only is the term problematic, in many usages it’s not even really right! In the IDE example the master/slave terminology is used just for coordination of a communication pipeline, and has very little to do with the master determining what the slave is doing. Primary/secondary would actually be better semantically