> Is there some 4chan-esque programming language that actually discourages queer people from using their language?
There isn't. I find that any organizations priding itself in employing (X) group of people is being disingenious at best, and preferential at worst.
Personal traits are irrelevant in a professional setting, let alone an online one where they are hidden away behind written communication. So to actively seek them out, or worse, place them on a pedestal, only signals that you reward personal traits over actual work ethic and ability. You're essentially taking pride in what your employees are rather than what your employees can do... Such organizations tend to go down a purity spiral of policing human interaction and speech, as well as preferential treatment of employees, to the detriment of product quality. Often implementing measures that are low in merit but high in potential for abuse, such as forcing contributors to sign vague agreements[1], or banning "offensive" numbers[2] from being used.
I wouldn't trust such an organization with my machine or data. The comments in the article do nothing but instill doubt in Rust's quality as a product and its future.
1. nobody is required to "sign" the code of conduct
2. That does not ban any numbers from being used. That is a lint in the compiler's codebase where they do not wish to have those being used in examples. only the compiler.
and why 0xCAFED00D? if this is a reference to something I don't get it and probably it shouldn't be there if it's not so popular that anybody knows about it.
the best I could find about it is "("cafe dude") is used by Java as a magic number for their pack200 compression."
Once again, I'm not involved in any way, so my opinion is irrelevant.
But sure: I don't know Italian slang. However, a project that conducts both itself and its examples in English not being comprehensive about possible meanings in other languages isn't exactly a gotcha. Furthermore, the example is suggesting that you don't pick at random, but instead something that is obviously not a word, like 0x12345678. It's not suggesting that you make something up.
Furthermore, this isn't something about trying to be "absolutely pure" or something. It's a helpful lint to catch common cases. Nothing more, nothing less.
There isn't. I find that any organizations priding itself in employing (X) group of people is being disingenious at best, and preferential at worst.
Personal traits are irrelevant in a professional setting, let alone an online one where they are hidden away behind written communication. So to actively seek them out, or worse, place them on a pedestal, only signals that you reward personal traits over actual work ethic and ability. You're essentially taking pride in what your employees are rather than what your employees can do... Such organizations tend to go down a purity spiral of policing human interaction and speech, as well as preferential treatment of employees, to the detriment of product quality. Often implementing measures that are low in merit but high in potential for abuse, such as forcing contributors to sign vague agreements[1], or banning "offensive" numbers[2] from being used.
I wouldn't trust such an organization with my machine or data. The comments in the article do nothing but instill doubt in Rust's quality as a product and its future.
[1] https://www.rust-lang.org/policies/code-of-conduct
[2] https://github.com/rust-lang/rust/blob/d0ea1d767925d53b2230e...