Slashdot Mirror

← Back to Stories (view on slashdot.org)

OpenJDK Bug Report Complains Source Code 'Has Too Many Swear Words' (java.net)

Posted by EditorDavid on from the professionalism dept.

Thursday a bug report complained that the source code for OpenJDK, the free and open-source implementation of Java, "has too many swear words." An anonymous reader writes: "There are many instances of swear words inside OpenJDK jdk/jdk source, scattered all over the place," reads the bug report. "As OpenJDK is used in a professional context, it seems inappropriate to leave these 12 instances in there, so here's a changeset to remove them."
IBM software developer (and OpenJDK team member and contributor) Adam Farley responded that "after discussion with the community, three determinations were reached":
  • "Damn" and "Crap" are not swear words.
  • Three of the four f-bombs are located in jszip.js, which should be corrected upstream (will follow up).
  • The f-bomb in BitArray.java, as well as the rude typo in SoftChannel.java, *are* swear words and should be removed to resolve this work item.

He promised a new webrev would be uploaded to reflect these determinations, and the bug has been marked as "resolved."


10 of 281 comments (clear)

  1. Well, for an expansive definition of "bug" by Geoffrey.landis · · Score: 4, Insightful

    That's a pretty wide definition of "bug".
    I'd think that maybe they could devote their debugging efforts to more annoying bugs...

    --
    http://www.geoffreylandis.com
    1. Re: Well, for an expansive definition of "bug" by Cylix · · Score: 4, Insightful

      That people who look for swear words in code have too much free time and too fragile personalities.

      --
      "You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
    2. Re: Well, for an expansive definition of "bug" by Dunbal · · Score: 5, Insightful

      What is your definition of annoying?

      People who go around looking at code comment sections and bitch about swear words while adding absolutely nothing to the actual code development. That's pretty fucking annoying.

      --
      Seven puppies were harmed during the making of this post.
  2. The rot is growing stronger by gweihir · · Score: 4, Insightful

    Obviously, we are moving more towards NewSpeak. It seems nobody reads the classics anymore and the same evil mistakes are getting prevalent again.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  3. Next it'll be git commit messages by Anonymous Coward · · Score: 4, Funny

    I can see the one for this ticket now:

    "Updated comments to remove 'fuck' 'shit' and 'bollocks' as some millenial wanker decided to complain. Pussy."

  4. Kill all the children... by Anonymous Coward · · Score: 5, Funny

    One of my favourite code comments came from a French Canadian coder in a shutdown routine for a Unix daemon process that spawned a lot of child processes where he wrote: "And now we kill all the children...".

  5. Heat by JBMcB · · Score: 5, Interesting

    I've seen very select cases where swearing in comments can be useful.

    There was a piece of code I saw that people thought was a bug, but was actually purposefully written a particular way to get around a bug in the compiler. Even after comments like // SERIOUSLY do not touch this it's a workaround for CVXXXXXX

    People kept messing with it. Finally the dev checked in // DO NOT F****ING TOUCH THIS

    and the regressions went away. Again, niche applications, but still valid.

    --
    My Other Computer Is A Data General Nova III.
  6. Changing the word won't make it so. by SchroedingersCat · · Score: 4, Insightful

    As if removing the words will make that monstrous ball of crap better.

  7. This is exactly why you should try not to swear by SuperKendall · · Score: 4, Insightful

    People kept messing with it. Finally the dev checked in // DO NOT F****ING TOUCH THIS - and the regressions went away.

    This is exactly why you should really try not to swear, in writing or in speech...

    It's because it cheapens the words, and they loose effect.

    These days if someone called you a motherfucker, it's kind of like calling you annoying. It has no power.

    The reason that comment kept people away is because swearing in code is still relatively uncommon, so it has power. So keep the F-bombs out of code, so when the time comes where it is needed, it still works.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  8. Bidirectionality abuse (5:erocS) by tepples · · Score: 4, Informative

    Vandals were abusing Unicode bidirectionality control characters to break the layout and spoof moderation scores, which I've called the erocS problem. A secondary problem is many other Unicode code points are more suited for making lewd "ASCII art" (in the broad sense) than for polite discussion using English language prose. How did SoylentNews, which runs a fork of Slashdot's software, solve these two issues?