61–70 of 278 posts
[1] https://www.vidarholen.net/contents/wordcount/#fuck*,shit*,d...*
[2] https://www.vidarholen.net/contents/wordcount/#fuck*,shit*,d...*
Theory: the shift towards lesser swearwords is a sign of corporatization, making the linux source a soulless bland hellscape of confirmity.
Hopefully in a few decades the last of the people who think that using respectful discourse means no fun can be had will be gone and we can stop rehashing these threads. You're contributing to something that runs on billions of devices across the world and is maintained by people around the world of all types. If you can't describe your code, your reasons, and your notes politely, do better.
I think so-called "professional" speech - which I'd call bland and often ineffective speech - is professional in the same way that a suit and tie is professional. It's a uniform to ensure nobody stands out, and the corporation can absorb everybody's personality, like flour incorporated into bread dough. White bread, no seeds.
Earlier quoted context omitted.
It seems like absolute count of occurrences, not normalized to codebase size. Even more informative would be to plot the occurance rate within new code.
OKR for H2: Increase edginess of Linux for a less corporate feel Key result: Boost occurrence of swearwords by 20% Key result: Create a new metric that tracks relative swearword use per line YoY Key result: Attract at least 100 comments on HN or Reddit about the new code
Theory: the shift towards lesser swearwords is a sign of corporatization, making the linux source a soulless bland hellscape of confirmity.
I have never worked on a big corporation. But I find interesting about corporations forbidding swearwords in code. I mean, the people responsible for forbidding swearwords rarely read code. And if they read code with any frequency and are somewhat proficient at it, most likely they have their own list of swearwords. Also we should look to add more keywords to programming languages that trigger naïve filters. I'm all…
1. Reputational harm in the event that code needs to be shared. Say, the code gets read in court, or an outside consultant is brought in who is given access to the code. The company likely wants to maintain the same standard of professionalism that they expect when their employees write or utter spoken language in the workplace for the same reasons.
2. Similar to #1 but nuanced enough to deserve its own mention: code is a business asset. It can be sold or licensed out. The company may fear that language that it deems unprofessional could depreciate the value of that code in the context of selling or licensing it to 3rd parties.
Personally I think that the fuss over "bad words" is deeply irrational to a religious degree. The idea that arbitrary sequences of phones or characters will cause anyone within ear or eye-shot to become offended is rather absurd. But you can't choose what planet you do business on and, on Earth, there are a lot of silly people.
Trying adding "ass", it explodes [1]. Not sure if that's because of keywords such as 'class' or something else? "dumb" is really on the uptake [2]. [1] https://www.vidarholen.net/contents/wordcount/#fuck*,shit*,d... * [2] https://www.vidarholen.net/contents/wordcount/#fuck*,shit*,d... *
Resolution: Behaving as expected. Won't fix.
Theory: the shift towards lesser swearwords is a sign of corporatization, making the linux source a soulless bland hellscape of confirmity.
They went up, actually. "crap" skyrocketed in the last years, and the rest were more or less stable.
Earlier quoted context omitted.
Hopefully in a few decades the last of the people who think that using respectful discourse means no fun can be had will be gone and we can stop rehashing these threads. You're contributing to something that runs on billions of devices across the world and is maintained by people around the world of all types. If you can't describe your code, your reasons, and your notes politely, do better.
There are two types of people: the ones that write the code, find the bugs (including hardware ones), find the bad design decisions (including the ones they wrote themselves)... and the ones that complain that they found a swearword in the source code they never see because compilation step. Or as they say in the army: do, lead, or get out of the way.
Earlier quoted context omitted.
I have never worked on a big corporation. But I find interesting about corporations forbidding swearwords in code. I mean, the people responsible for forbidding swearwords rarely read code. And if they read code with any frequency and are somewhat proficient at it, most likely they have their own list of swearwords. Also we should look to add more keywords to programming languages that trigger naïve filters. I'm all…
I don't personally care about language choices in code, but I'll play devil's advocate and speculate as to why a business might be concerned. 1. Reputational harm in the event that code needs to be shared. Say, the code gets read in court, or an outside consultant is brought in who is given access to the code. The company likely wants to maintain the same standard of professionalism that they expect when their employ…
Trying adding "ass", it explodes [1]. Not sure if that's because of keywords such as 'class' or something else? "dumb" is really on the uptake [2]. [1] https://www.vidarholen.net/contents/wordcount/#fuck*,shit*,d... * [2] https://www.vidarholen.net/contents/wordcount/#fuck*,shit*,d... *
Earlier quoted context omitted.
I have never worked on a big corporation. But I find interesting about corporations forbidding swearwords in code. I mean, the people responsible for forbidding swearwords rarely read code. And if they read code with any frequency and are somewhat proficient at it, most likely they have their own list of swearwords. Also we should look to add more keywords to programming languages that trigger naïve filters. I'm all…
I don't personally care about language choices in code, but I'll play devil's advocate and speculate as to why a business might be concerned. 1. Reputational harm in the event that code needs to be shared. Say, the code gets read in court, or an outside consultant is brought in who is given access to the code. The company likely wants to maintain the same standard of professionalism that they expect when their employ…
Depends a lot on the culture. In the countries I've worked in, anyone trying to forbid profanity in the workplace would be laughed out of the room. The laughter would likely turn to anger if it turned out to be Americans trying to impose puritanism on another country's project