This is a dumb debate. I use whatever terminology the documentation does. Master/Slave, Primary/Secondary, Primary/Replica - I don’t care. If “slave” upsets people & changing it makes them more comfortable why cry over it? Just use a different word.https://twitter.com/randileeharper/status/933403294919139328 …
I think the key point here is to deprecate old terminology gracefully. Other terms should be preferred for new developments, but existing usage shouldn't be forced to change (especially not if it requires significant refactoring or, worse, interface changes).
-
-
Well interface changes are part of any terminology change: Terminology IS, by definition, an interface. It changed in DNS and (many) database systems without the world ending. Our natural aversion to change is not an adequate reason to stomp our feet & refuse like petulant kids
-
I'm thinking specifically about *programmatic* interfaces, not human ones. As you say, human brains are good at adapting to change. Computers aren't. Changing docs? Sure. Renaming library functions and breaking ABI? Please don't. At least wait until something else breaks ABI.
- Show replies
New conversation -
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.