Microsoft's adoption of the Chromium browser engine developed by Google for Edge has resulted in a proposal to clean the open source code from "potentially offensive terms."
The number 981129 in the Chromium error log lists a suggestion by Microsoft for "Clearing potentially offensive terms in the code base" aims to eliminate language software blueprints such as the whitelist (change to permission list), blacklist (switch to block list), "offensive terms that use & # 39; wtf & # 39; as protocol messages" and other unhappiness.  This error report was generated by a Microsoft collaborator, who stated: "We are simply sharing a subset of what PoliCheck scanned for us," Policheck is "a machine-learned model that other equipment handles that does based scanning. in context in hundreds of file formats. ”
Googler Rick Byers, a Chromium engineer, gave a cautious welcome to the subject, saying:" This seems like a good strategy, thanks for doing so! Certainly we have never intended a whole in the code base can be potentially offensive, but I am also not aware that anyone makes an effort to find them all. "He added:
Although changing comments or variable names in the Source code is generally invisible to the user, this type of review can be problematic if it destroys things like names in preferences and policies.
Judging by the relatively short list of issues, the Chromium source code is already, for the most part part, clean, as corresponds to a body of public code.
What the @ # $% &!? Microsoft prohibits nudity, insults on Skype, emails, Office 365 documents
Opinions will vary on the value of such changes, although if Microsoft takes its diversity and inclusion policy seriously, it is not surprising that the language used in code or source falls under these rules. Google also has a pro-diversity program, as expected.
In May, Microsoft announced artificial intelligence functions in Word that, among other functions, will issue "advice on a more concise and inclusive language, such as" police officer. "Of & # 39; police & # 39;".
The PoliCheck tool seems to have existed somehow for a long time. "Reading that Policheck file was … incredibly educational. I learned all kinds of exotic curse words I didn't know before," commented developer Andrew Gaspar, who He described himself as "formerly Windows Core Engineering at Microsoft." The discussion concerned the source code of Windows 2000 leaked in 2004, which claimed to contain many references to idiots and fools, although "there were no racist or homophobic insults." ®