2 ms·
This is a good example of why master/slave is not an accurate term: most technical uses reflect performing the same kind of work rather than one only telling th
by acdha 6y ago
This is a good example of why master/slave is not an accurate term: most technical uses reflect performing the same kind of work rather than one only telling the other what to do and when the master fails a slave is elected to replace it. Your master database doesn’t torture the slave node when it errors, either.
Using more accurate terms such as those on the kernel’s list immediately tells you the nature of the relationship AND doesn’t make anyone uncomfortable. That seems worth it alone, and it’s really unclear what good reason could explain why a few people would spend far more time complaining about work which someone else will do than it will take to complete that work.