Reply to post: We need to solve this once and for all

Allowlist, not whitelist. Blocklist, not blacklist. Goodbye, wtf. Microsoft scans Chromium code, lops off offensive words

Any other name
Gimp

We need to solve this once and for all

The best and the surest way to resolve this recurring controversy is quite clear to me: we must remove all extraneous nouns, verbs and adjectives from all source code and all messages communicated to the users. After all, essentially any word, or a word which is spelled almost the same, or a word which sounds almost the same, or a pictogram which looks kind of similar after folding the printout of the source into an exquisite origami chrysanthemum will be offensive to someone somewhere in some of the languages we speak.

From now on, we shall refer to all functions, methods, and variables by their decimal ordinal numbers. If the computer language specification requires so, then until the specification can be corrected it shall be permissible to insert a single letter at the beginning of the designator. To avoid giving offense, that letter shall be same for all source files within a project tree. Numbers 4, 9, 13, 17, 39, 666, as well as all other numbers deemed offensive by the Supreme Peoples' Denumeration Triumvirate shall not be used and shall be retroactively removed from all sources.

That ought to take care of most of the problem.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

SUBSCRIBE TO OUR WEEKLY TECH NEWSLETTER

Biting the hand that feeds IT © 1998–2019