Slashdot Mirror

← Back to Stories (view on slashdot.org)

Comment Profanity by Language

Posted by CmdrTaco on from the dumb-dumb-stupid-face dept.

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.

14 of 263 comments (clear)

  1. Perfect? by SatanicPuppy · · Score: 4, 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.

    --
    ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    1. Re:Perfect? by Lord+Ender · · Score: 4, Funny

      Perl programmers never put in profane comments, because cursing in Perl itself is much more satisfying.

      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.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    2. Re:Perfect? by mkiwi · · 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)

  2. C++ Templates by Bloodwine77 · · Score: 3, Funny

    C++ Templates will turn the most pious programmer into a curse-slinging, chain-smoking alcoholic.

  3. Also a bar chart! by Abstrackt · · Score: 5, Funny

    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
  4. Isn't profanity a part of C++? by ibsteve2u · · Score: 2, Funny

    Like isn't polymorphism a reference to the ability to fuck anything up - with class?

    --
    Orwell: "In a Time of Universal Deceit, telling the Truth is a Revolutionary Act"
  5. Re:Perfection. by mini+me · · Score: 4, Funny

    Ruby only scored so high because of David Heinemeier Hansson. Source: http://farm1.static.flickr.com/47/127984254_ddd4363d6a.jpg

  6. PHP For The Fucking Win by Anonymous Coward · · 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.

  7. Visual Basic? by PPH · · Score: 1, Funny

    ' Mom! Why doesn't this code work? Can I have a cookie and fix it later?

    --
    Have gnu, will travel.
    1. Re:Visual Basic? by sqldr · · Score: 3, Funny

      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.
  8. Re:PHP programmers by TheRaven64 · · Score: 5, Funny

    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
  9. No tits ? by Yvanhoe · · Score: 3, Funny

    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. Not just the comments by 6Yankee · · Score: 4, 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!

  11. Re:Perfection. by maxwell+demon · · 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. :-)

    --
    The Tao of math: The numbers you can count are not the real numbers.