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'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.
-
-
This is what major version numbers are for. If nothing else except the front-end terminology ever changed then at some point you should still change the code to be consistent so you don't confuse devs. Dual support, deprecation, warnings, removal - just like any other change.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.