Slashdot Mirror
Comment Profanity by Language
beret found a nifty little pie chart breaking down
profanity in code comments broken down by language. He used Carlin's Seven Words, and C++ came out on top while PHP users are either wholesome or perfect.
← Back to Stories (view on slashdot.org)
More like they never fucking comment their motherfucking code.
Perl programmers never put in profane comments, because cursing in Perl itself is much more satisfying.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
C++ Templates will turn the most pious programmer into a curse-slinging, chain-smoking alcoholic.
There's also a bar chart because somebody couldn't interpret the pie chart....
They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance. - Terry Pratchett
Ruby only scored so high because of David Heinemeier Hansson. Source: http://farm1.static.flickr.com/47/127984254_ddd4363d6a.jpg
Actually, contrary to the summary, this article has nothing to do with code comments, and so the amount of comments per code has no effect on the results. The profanity measured in the article is from git commit messages.
As a goddamn PHP programmer, I am fucking glad that those cocksuckers don't put a lot of profane shit in the fucking comments. Unlike those asshole C++ programmer bastards. Goddamn cunts.
PHP programmers have such a low number of profanities in comments because they have yet to learn to comment their code.
I am TheRaven on Soylent News
When I was in high school many moons ago I wanted to get into a programming class but my grades weren't good enough so I had to submit some programming work to the teacher. I gave her the source code for a BBS I had written. I remember having to go through the entire source base looking for profanity I had used in variable names, comments, etc. Being the teenager that I was I would sometimes just use them for no reason.
I remember laughing to myself when I handed her that code. It must have been over 200 pages of printed source and I could tell she probably couldn't even write a sort function. This was back in the 80's when the educational system had almost no computer classes, let alone programming.
It was at that time I realized that sometimes other people look at your code and it can reflect on you. I have never used profanity in source ever again. I also never berate other people's stuff in my code (like poorly written API's I have to use). Clean and professional makes for more readable code and keeps everyone happy, including myself.
The ratio of people to cake is too big
As expected, no tits showed up in millions of git commits.
The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
10 years later.. why DOES this code work? and what the hell was in those cookies?
I wrote my first program at the age of six, and I still can't work out how this website works.
Shit, Piss, Fuck, Cunt, Cocksucker, Motherfucker, Tits
to you too!
On my last project, someone added a third-party Javascript calendar. I was horrified to discover that it had a function called continuationForTheFuckingKHTMLBrowser().
It's one thing if it's server-side code, and I'll occasionally slip up and put "wtf" in a PHP comment (usually in some "never happen" safety block). But don't do it where inquisitive and technical users (of which we had several) can get at it. And certainly not in code that's intended for others to expose to *their* users.
After I'd renamed that function and committed, I searched the entire project for every swear word I could think of. Amusingly, though the rest of the source was clean, buried in the bytecode of our packaged-up WAR file was the sequence upper-case F, lower-case u, c, k, exclamation mark. Even the compiler was at it!
Php showed up as perfect because it is almost perfectly comment free.
This is an indictment of the language, not the programmers, since well-commented php is drastically slower (like .5% tomg!) than stripped down and nearly obfuscated code. That fraction really adds up when you have all those unnecessarily dynamic web pages to generate.
Now if someone were to do a comparison on the ratio of active code, to code that is commented out but not removed because the author doesn't use version control... In that category PHP would freaking rule!
Innocent people shouldn't be forced to pay for inferior software development.
--"Code Complete" Microsoft Press
The PHP interpreter tends to get bored with executing the code, and then browses the repositories. The less comments there are in the commit messages, the less time the PHP interpreter spends reading them, and the more time it can use to actually interpret the code. :-)
The Tao of math: The numbers you can count are not the real numbers.