> Replacing one well known default with another non-retroactively increases cognitive load.
It's quite clear that managing cognitive loads is the least of all concerns considered by proponents of sticking with non-inclusive terms.
For example, the terms "blacklist"/"whitelist" do not impose a lower cognitive load than "denylist"/"allowlist", but somehow this argument is used in favour of sticking with the legacy/non-descriptive terms.
Also, there is no objective meaning to "slave". In the times of old, people talked about "slave drives" and I bet that most of the proponents of sticking with racist/bigoted language cannot even describe what it's supposed to be.
It's quite clear that managing cognitive loads is the least of all concerns considered by proponents of sticking with non-inclusive terms.
For example, the terms "blacklist"/"whitelist" do not impose a lower cognitive load than "denylist"/"allowlist", but somehow this argument is used in favour of sticking with the legacy/non-descriptive terms.
Also, there is no objective meaning to "slave". In the times of old, people talked about "slave drives" and I bet that most of the proponents of sticking with racist/bigoted language cannot even describe what it's supposed to be.