4 ms·
Here we go again. But seriously, what's wrong with using "primary" and "replica" in a database context? They're generally clearer terms anyway. Obviously we'll
by zozbot234 6y ago
Here we go again. But seriously, what's wrong with using "primary" and "replica" in a database context? They're generally clearer terms anyway. Obviously we'll be stuck talking about "master" and "slave" IDE connectors and the like, but other than that it seems to be falling out of use pretty much everywhere.
- messe 6y agoAlso on the topic of Whitelist/Blacklist, I thought it was stupid to go about renaming, but then I saw the alternative was Allowlist/Blocklist, which IMO is much clearer (doubly so for non-native speakers).
- rgoulter 6y ago> But seriously, what's wrong with using "primary" and "replica" in a database context Those terms are fine. The practical argument to change the terms because you think they're clearer isn't a compelling reason to change the terms. But, also, a practical argument doesn't really mix well with the moral argument. (If "master"/"slave" were better understood than alternatives, but agreed to be offensive, would it be better to use those terms?). I don't see the argument as to being about which terms are best, though. The contention is 'the terms "master"/"slave" are offensive, and should be changed'. In terms of "what's wrong": this discussion has enough comments in favour of / against the idea to get a sample of what people are disagreeing about. If I understand correctly: "it's a small change to make, that will reduce the exclusion some people feel", and "the terms aren't used in an offensive way, it's not of substantial worth to change it".