Avoid master/slave terminology

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.

... bad if talented people who could be doing something more important (which includes absolutely anything) are forced to waste their time either doing this or arguing why they shouldn't be.

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