Just a thought, what if we made the world a better place through clearer terminology? It's not a major improvement, but it helps reduce friction in communicatio

Just a thought, what if we made the world a better place through clearer terminology? It's not a major improvement, but it helps reduce friction in communications. Ignoring connotations, master/slave is pretty unclear to me and needs more explanation. I've seen it used to describe: * a coordinator with a worker pool in which the coordinator sends jobs to the workers for actual computation * a designation of where on the bus a device sits * a designation of which copy is the source of truth/gets writes (master) compared to the read only copies * a designation of which instance is currently doing the work vs which is the standby in an active-active failover Yes those are all similar, but it's annoying to hear someone say "this is configured in a typical master/slave pattern" only to be left wondering which of the above applies. I guess we could make some sort of purity argument about which of these is the one-true use for master/slave. Or we could differentiate the cases with more applicable and descriptive words. As a bonus some folks aren't offended.