Comment Profanity by Language 263
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.
Perfect? (Score:5, Funny)
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.
C++ Templates (Score:3, Funny)
Also a bar chart! (Score:5, Funny)
Isn't profanity a part of C++? (Score:3, Funny)
Re:Perfection. (Score:5, Funny)
Ruby only scored so high because of David Heinemeier Hansson. Source: http://farm1.static.flickr.com/47/127984254_ddd4363d6a.jpg [flickr.com]
PHP For The Fucking Win (Score:5, Funny)
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.
Visual Basic? (Score:2, Funny)
' Mom! Why doesn't this code work? Can I have a cookie and fix it later?
Re:Perfect? (Score:5, Funny)
I love Perl programs, like I love the Perl stack-traces. I have sampled every language, Perl is my favorite. Fantastic language. Especially to curse with. It's like wiping your ass with unix.''=~('(?{'.('/_)@){'^'_-@.][').'"'.('___[^'^'-*="|').',$/})'). I love it.
Re:PHP programmers (Score:5, Funny)
No tits ? (Score:4, Funny)
Re:Visual Basic? (Score:4, Funny)
Re:Perfect? (Score:4, Funny)
I agree with parent. Although, since I started coding using Objective-C naming conventions (even in other languages), I've found that many comments are unnecessary. When you have a method called:
putTextPaneFromSearchBoxInMainNSView(TextPane * textPane, NSView * primaryView)
it's pretty clear what it means. I don't think many python programmers have learned that style yet, thus you see the problems with the code. (My experience, YMMV)
Not just the comments (Score:5, Funny)
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!
Re:Perfection. (Score:3, Funny)
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. :-)