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 somersault · · Score: 4, Interesting

      More like they never fucking comment their motherfucking code.

      My thinking exactly. Anyone who writes in PHP probably is using it because it's the easiest option..

      --
      which is totally what she said
    2. Re:Perfect? by Dayze!Confused · · Score: 4, Informative

      Really the title of the /. article is misleading, it is Commit Profanity by Language, which is entirely different.

      --
      "All tyranny needs to gain a foothold is for people of good conscience to remain silent." [Thomas Jefferson]
    3. Re:Perfect? by TheRaven64 · · Score: 5, Insightful

      In my personal opinion, developers like you are the reason why every single 'working' piece of Python code I've encountered has required me to spend time debugging it before actually using it.

      --
      I am TheRaven on Soylent News
    4. 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.
    5. Re:Perfect? by eln · · Score: 5, Insightful

      Most people skilled in a language (yes, even perl) can figure out what a piece of code actually does given enough time to look through it. The comments are to tell us what the code is *supposed* to do and *why*, so when we need to debug it we know what you were thinking when you wrote it and what you were trying to accomplish. When you're trying to figure out why a piece of code doesn't do what it's supposed to do, it's very helpful to know what it was supposed to do first.

    6. 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. 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
  3. 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

  4. NOT CODE COMMENTS!! by iYk6 · · Score: 5, Informative

    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.

  5. 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.

  6. 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
  7. I remember having to do that once by Cthefuture · · Score: 4, Interesting

    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
  8. 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!