So here's a question, particularly for POCs. Is "master" a problematic word when not juxtaposed with "slave"? My guess is not, because the word has a much broader meaning in English, but I'd like to hear your thoughts.
-
Show this thread
-
Example usages: master document, audio master(ing)/master recording, master of an art/technique, master of ceremonies, git master branch, etc. All seem pretty standard and free from slavery connotations, but I'm not qualified to opine.
8 replies 3 retweets 23 likesShow this thread -
Replying to @marcan42
Master / slave has no reason to be bad unless it is in relation to people. It makes perfect sense for databases etc.
1 reply 0 retweets 3 likes -
Replying to @sbingner
Nah, master/slave is bad terminology in tech because it's overloaded too much. "primary/replica" is a lot more descriptive for databases, or "active/standby" for automated failover styles in particular. master/slave doesn't say much.
2 replies 1 retweet 3 likes -
Replying to @marcan42
But in sql replication the replica isn’t a copy, it actually executes all the same commands as the master as the log is sent over, and it’s not standby as you can query it. You can have dual master/slave even where both sides are both master and slave, active/standby doesn’t work
1 reply 0 retweets 0 likes -
Replying to @sbingner
SQL replication can be accomplished multiple ways, SQL log shipping is just one of them :-) But either way, primary/replica works just fine. You can still query the replica (read-only) and changes to the primary are replicated to the replica.
1 reply 0 retweets 0 likes
The thing with master/slave is that it means... nothing. Just some vague notion of hierarchy. It is used in so many systems with different meanings that it has lost all nuance.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.