Word usage guidance and alternative terms

Re:Word usage guidance and alternative terms by Mordisquitos on Monday April 19, 2021 @10:07AM (#26862901)

Are they? Are the terms "whitelist" and "blacklist" used only in the context of "allowing" and "blocking"? Who or what is the subject that is implied to be "allowing" and "blocking" the elements of each list? Is the process involved in "allowing" and/or "blocking" passive or active?

"Whitelist" and "blacklist" are abstract terms which are useful because they have general and non-specific meanings which can be adapted to many contexts. Artificially prescribed alternatives, introduced only to satisfy the current American cultural Zeitgeist, are not.

[ Parent | on HN ]

Re:Word usage guidance and alternative terms by fanf2 on Monday April 19, 2021 @10:19AM (#26863012)

If you aren't using the list for allowing or blocking, then give it a name that describes what you are using it for.

It dismays me to see programmers arguing loudly and stubbornly for bad terminology, when a key skill for designing a good API is to choose good names.

[ Parent | on HN ]

Re:Word usage guidance and alternative terms by Mordisquitos on Monday April 19, 2021 @10:56AM (#26863421)

If only so much other "bad terminology" in IT that does not accurately reflect what it means, such as POST, PUT, cookie, bug, shell, etc. were also names of discriminated social groups in America... maybe then we could get people arguing loudly and stubbornly to replace them. One can only dream.

[ Parent | on HN ]

Re:Word usage guidance and alternative terms by slver on Monday April 19, 2021 @03:28PM (#26866952)

I propose we rename GET, POST, PUT, DELETE, PATCH to: SAFE, NOTSAFE, NOTSAFE, NOTSAFE, NOTSAFE.

[ Parent | on HN ]

Re:Word usage guidance and alternative terms by foobiter on Monday April 19, 2021 @08:35PM (#26869443)

you didn’t even give a single counter example

[ Parent | on HN ]