Slashdot Mirror


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

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


121 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 Geoffrey.landis · · Score: 2

      What is your definition of annoying?

      Well, software that freezes for no apparent reason is annoying, to start.

      --
      http://www.geoffreylandis.com
    2. Re: Well, for an expansive definition of "bug" by MrMr · · Score: 1, Offtopic

      I find people pretending to own an ios device by deliberately typing â(TM) instead of ' rather annoying.

    3. Re:Well, for an expansive definition of "bug" by SirSlud · · Score: 1

      You would think you have better things to do, like eat, drink, work, sleep than comment on a /. story.

      Actually not too many people would think that because they'd recognize that we can do lots of things. In your code bases, do minor and easy to address bugs never get addressed on the basis that there 'should be more important bugs'? See how stupid that sounds?

      --
      "Old man yells at systemd"
    4. Re: Well, for an expansive definition of "bug" by Cmdln+Daco · · Score: 1, Offtopic

      Apple just needs to deprecate 'Dumbquotes' to default as off, so people with iGadgets don't spam us with buggy comments.

    5. 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
    6. Re: Well, for an expansive definition of "bug" by CrashNBrn · · Score: 1

      It is belligerence, the "red site" (soylent) fixed all the outstanding Slashcode bugs, along with quality-of-life improvements, with a single developer over the course of 6-8 weeks.

    7. Re: Well, for an expansive definition of "bug" by Aboroth · · Score: 1

      I did not say that I cared what they thought, or even that anybody should care. All I said was that religious people are more likely to dislike swearing than SJWs. Be careful, your hatred is making you retarded.

    8. 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.
    9. Re:Well, for an expansive definition of "bug" by phantomfive · · Score: 1

      But now the committer can put on their resume "Committed code to OpenJDK."

      --
      "First they came for the slanderers and i said nothing."
    10. Re:Well, for an expansive definition of "bug" by thegarbz · · Score: 1

      debugging efforts

      If running grep to find some swear words is your definition of "effort" then you have no business commenting on how someone manages code.

    11. Re: Well, for an expansive definition of "bug" by Malc · · Score: 1

      Well I ainâ(TM)t no millennial (see my UID). Sounds like you worked at a place with no code review. Even old school places with any gumption have better engineering processes then you describe, and I work at place that develops SDKs with a C API, uses C++11 and assembly optimises important parts of the code. Macros are sometimes important to extend a language to features it doesnâ(TM)t have natively, but donâ(TM)t take the piss.

    12. Re: Well, for an expansive definition of "bug" by zbaron · · Score: 1

      ... or drink water from the wrong cup.

    13. Re: Well, for an expansive definition of "bug" by HornWumpus · · Score: 1

      Try following a canadian coder. Variables and function names can't contain the letter sequence 'eh' as that's defined as ';'!

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    14. Re: Well, for an expansive definition of "bug" by LordWabbit2 · · Score: 1

      Disagree, there is no reason whatsoever to be disrespectful, even in comments.
      You may not give a shit, but others do, just don't fucking do it.


      Which reminds me of when I started working as a programmer on an A-Series mainframe, was trying to find a bug and had the equivalent of "ECHO" in my code, and because I was getting frustrated I started using comments like "Yay, got fucken here" next minute my phone rings and on the other end is a religious type operator and he complained that he could see my comments and did not appreciate it. It got escalated rather rapidly and my manager had to step in and calm shit down. Learnt from that, I no longer put swear words into code or comments where someone else might end up working / maintaining it, which is pretty much all work related code. My team may not give a fuck either way but at some point some religious nut job is going to get employed and he will give a crap. My own private crap I swear the fuck away, because no one else is ever likely to see the code or comments.

      Which reminds me of another story, was working for a sports betting company, in the initial interview they asked me if I have any issues with betting, I was "Well if you suck at math then go ahead and waste your money" a while later we hired a Jehovah's Witness guy, he worked there for about a month before his church elders found out where he was working and forced him to resign. Like I said, you got to watch out for the nut jobs.

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
    15. Re: Well, for an expansive definition of "bug" by Aboroth · · Score: 1

      Haha, my post got modded "Troll" by the anti-SJW crusaders. Looks like they are easily offended special snowflakes, just like the SJWs they hate so much.

  2. Yeah ... by cpurdy · · Score: 2, Insightful

    Fuck this shit ...

    1. Re: Yeah ... by Anonymous Coward · · Score: 1

      I don't think this is outraged.. it is about professionalism.. if they want to be taken seriously code/comments etc should reflect that

    2. Re: Yeah ... by edris90 · · Score: 2, Insightful

      Those who prioritize social constructs such as professionism above function , are not mentally capable of the technical focus required to work in a technical field. If those are your priorities maybe you should be in a debate Forum instead arguing ethics for a living

    3. Re:Yeah ... by phantomfive · · Score: 2, Funny

      The world changes. Who would have guessed that the party on the left would become the prudes? Next we'll hear that Republicans want to legalize prostitution.

      --
      "First they came for the slanderers and i said nothing."
    4. Re: Yeah ... by jd · · Score: 1

      Those who prioritize quality in code don't use Windows, Linux, *BSD or any other general purpose OS, except as a text editor. And, frankly, I doubt more than three or four of us use Slashdot.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    5. Re:Yeah ... by DontBeAMoran · · Score: 1

      Next we'll hear that Republicans want to legalize prostitution.

      As long as they can tax it as health services you bet they'll approve it.

      --
      #DeleteFacebook
    6. Re:Yeah ... by phantomfive · · Score: 1

      Apparently health services aren't a tax anymore. Well well well, three holes in the ground.

      --
      "First they came for the slanderers and i said nothing."
    7. Re: Yeah ... by astrofurter · · Score: 1

      Which OS, then, is preferred by those who prioritize quality in code?

    8. Re: Yeah ... by Falos · · Score: 1

      Punch cards

    9. Re: Yeah ... by edris90 · · Score: 1

      At its most extreme? Bare metal assembly.

  3. Reasonable approach by rsilvergun · · Score: 1

    let the programmers & community decide by up-voting this if they care.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Reasonable approach by Anonymous Coward · · Score: 1

      Cunts with no life. They spend so much time on inane bullshit because they've convinced themselves they're doing something worthwhile. So cunts with no life who feel righteous about it.

      Oxygen thieves the lot of them.

    2. Re:Reasonable approach by DontBeAMoran · · Score: 1

      That's the problem with sjws. They're cunts. One person can out-vote a majority or cause a lot of damage given their incredible motivations for their own agendas.

      "'We can't win against obsession. They care, we don't. They win." — Douglas Adams

      --
      #DeleteFacebook
  4. 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.
    1. Re:The rot is growing stronger by alvinrod · · Score: 1

      Don't you mean the same doubleplusungood mistakes?

    2. Re:The rot is growing stronger by jmccue · · Score: 2

      Nah, singleplusgood

      But I would like to know. what self respecting programmer even reads the comments

    3. Re:The rot is growing stronger by swillden · · Score: 1

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

      Come off it, avoiding profanity in written professional communication is hardly equivalent to NewSpeak.

      Sheesh, some people just like getting worked up, I guess.

      I should mention that IMO this includes people who get annoyed enough about swear words in source code to find them and submit patches to remove them.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    4. Re:The rot is growing stronger by dryeo · · Score: 1

      Well what should we do about the religious snowflakes? Perhaps get rid of freedom of religion and as someone above suggested, murder all the religious right wing nut jobs that are so easily offended by body parts and natural things like sex?

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    5. Re:The rot is growing stronger by AmiMoJo · · Score: 2, Insightful

      While I personally don't five a flying fuck about swearing in source code and can't really see how it could be an issue when using the JDK in a "professional" environment, you are massively over-reacting.

      If the source contained stuff like personal attacks, doxing, or giant ASCII penises that stuff would probably be removed for what are hopefully obvious reasons. So clearly there are already some standards in place that have been widely enforced for as long as modern English has existed, and didn't cause any problems.

      Not to mention the absurdity of not wanting a few widely recognized impolite words that have been banned in many areas such as pre-watershed TV forever being equated to the fall of civilisation into fascism or whatever it was you were alluding to.

      It's very hard to have a reasonable discussion about this when the first post is such an extreme over-reaction.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    6. Re:The rot is growing stronger by NicknameUnavailable · · Score: 1

      Obviously, we are moving more towards NewSpeak.

      We've had newspeak for awhile, just look at "regulation" - it means "to ensure a machine is well oiled, tuned, and calibrated." That didn't fit the narrative so in modern terminology it means "to restrict" because that allows gun grabbers to claim "it always meant no assault butter knives, assault butter knives were never intended by the founding fathers." Pretty big distinction from "you should all be armed to the teeth and well trained to use your arms" as they originally intended.

    7. Re: The rot is growing stronger by jd · · Score: 1

      NewSpeak is what American Republicans, Libertarians and Democrats use.

      Those left may or may not, depends on the day.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    8. Re: The rot is growing stronger by jd · · Score: 1

      The idea of open source being that if you don't like something, you write fixes. Sorry, the procedure worked entity as designed. If there are undocumented features to it, submit patches.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    9. Re:The rot is growing stronger by djinn6 · · Score: 3, Insightful

      Open source is a hobby, not a profession. Yes, there are some people who are paid to create open source software. They can censor their own communication if they so desire, or their boss might force it upon them, but they do not have a right to control others.

      IMO if a particular curse word is the best way to communicate something, then they should use it without reservation. E.g. writing "this implementation makes no fucking sense" communicates a very different level of confusion and urgency than "this implementation makes no sense" or "this needs to be refactored asap".

      Personally, if I saw that in the code base, I would not remove the curse word until I'm able to refactor the code and make the comment obsolete.

    10. Re:The rot is growing stronger by swillden · · Score: 1

      Open source is a hobby, not a profession.

      To a first approximation, no widely-used open source software is written by hobbyists. OpenJDK certainly is not.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    11. Re:The rot is growing stronger by AuMatar · · Score: 1

      No, its mostly a profession these days. In the major open source projects, the number of people paid to contribute by major tech companies vastly outnumber the number of hobbyist coders.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    12. Re:The rot is growing stronger by AHuxley · · Score: 1

      Should a "professional" environment want good code they can pay for that their own clean code.
      Using their own staff. Hire staff to write code for them that is "professional".
      Why should anyone have to worry about their code been '"professional" and what "environment" then later selects to use that code.
      Who gets to set the SJW standards? The people who work on the code every day?
      A '"professional" who later wants to use that code?

      --
      Domestic spying is now "Benign Information Gathering"
    13. Re: The rot is growing stronger by astrofurter · · Score: 2

      "avoiding profanity in written professional communication"

      Professionalism is when you hold your work product to a high standard, and refuse to obey unethical orders.

      What this human turd is doing, censoring strong language, is _prudery_ not professionalism.

    14. Re:The rot is growing stronger by Waccoon · · Score: 1

      Most people are so desensitized to foul language that swear words don't convey urgency.

    15. Re:The rot is growing stronger by AmiMoJo · · Score: 1

      I'm starting to suspect that the compiler doesn't...

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    16. Re:The rot is growing stronger by goose-incarnated · · Score: 1

      Well what should we do about the religious snowflakes? Perhaps get rid of freedom of religion and as someone above suggested, murder all the religious right wing nut jobs that are so easily offended by body parts and natural things like sex?

      That's funny - the people asking to silence me aren't from the right. The people actually succeeding in silencing others also aren't from the right.

      --
      I'm a minority race. Save your vitriol for white people.
    17. Re:The rot is growing stronger by AmiMoJo · · Score: 1

      Linux has benefitted immensely from commercial contributions. In fact the majority of work is now done by people being paid to do it. I don't know about JDK but it seems similar.

      Seems that for the sake of retaining a few swear words out of the source that could be a big loss.

      As to who decides, I guess it's the same SJWs who decided you masturbate in public, i.e. fascists.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    18. Re:The rot is growing stronger by HornWumpus · · Score: 1

      It will be 'working as required' when the snowflake is ostracised.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    19. Re: The rot is growing stronger by HornWumpus · · Score: 1

      The procedure will be working when someone trying to diff for changes reverses these useless edits.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    20. Re:The rot is growing stronger by HornWumpus · · Score: 1

      Comments by the coder aren't the same as comments from random idiots.

      Your hypothetical should never happen, as the commenter wouldn't have checkin rights. They could of course fork the project to add their editorials.

      Four 'fucks' in a project is not overuse of cursing. Bet there are four messes in there that rate 'fucks'.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    21. Re:The rot is growing stronger by HornWumpus · · Score: 1

      Idiot. The word that matters is 'people'. As you point out, they clearly knew the word 'militia' have just used it earlier in the sentence.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    22. Re:The rot is growing stronger by AHuxley · · Score: 1

      When skilled people who do the "commercial contributions" write all the code they can set what is "professional" in their code. Then give the "code" away for free?
      Until then anyone who actually writes great code for free in their own time can use any comments they want in their own code.
      Code they publish for free that everyone can use... ie its their own content, comments and all :)

      Freedom is like that. People who do the actual work get to work in any way they want.
      People then have the freedom to use the code. To go their own way with their "commercial contributions" and "professional" use of comments.

      --
      Domestic spying is now "Benign Information Gathering"
    23. Re:The rot is growing stronger by dryeo · · Score: 1

      I guess they've already succeeded in making your speech correct. For me, it has always been the right that gets upset and censors shit, and fuck. try going on national TV during children's hour and say fuck and see which side responds, or worse, show a female boob, even with the nipple covered during the superbowl.

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    24. Re:The rot is growing stronger by goose-incarnated · · Score: 1

      I guess they've already succeeded in making your speech correct. For me, it has always been the right that gets upset and censors shit, and fuck. try going on national TV during children's hour and say fuck and see which side responds, or worse, show a female boob, even with the nipple covered during the superbowl.

      Is that better or worse than shutting down speech? Or cry-ins after an election? Or university students standing with "This is not a free-speech zone"? Or "blaming the russians" without a single shred of evidence even after 24 months? How about "as majority group members you don't get to argue"?

      For me, mobbing people for wrongthink is worse than protesting when children's programs say "fuck". You may have a different standard, one in which it is okay to implement 1984, but you don't get to castigate the egalitarians because we don't agree that speech should be shut down.

      --
      I'm a minority race. Save your vitriol for white people.
  5. 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."

    1. Re:Next it'll be git commit messages by K.+S.+Kyosuke · · Score: 1

      "Also, we've removed all instances of 'java' as well."

      --
      Ezekiel 23:20
  6. 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...".

    1. Re:Kill all the children... by Kjella · · Score: 1

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

      It's all well and fun until you hit the wrong person. I remember reading a story, it might have been on the daily WTF but I couldn't find it about a guy who called up a coworker about a "child killed" problem. There was just a *click* then no answer... a colleague filled him in, the other type of "child killed" just recently. Ouch.

      --
      Live today, because you never know what tomorrow brings
  7. Challenge Accepted by SirDrinksAlot · · Score: 1

    Mental note: Next utility I don't want to make will be entirely constructed using profanity.

    Just need to work out the style guide for it now, high level is open to discussion.

    1. Re:Challenge Accepted by Mal-2 · · Score: 1

      You could fork Ook to use whatever word you want.

      --
      How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
  8. 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.
    1. Re:Heat by Anonymous Coward · · Score: 1

      Isn't this the purpose of language?

      If " don't touch this" fails to communicate your thoughts but "DONT'T FUCKING TOUCH THIS" succeeds,
      I would argue that's an effective improvement in communication, not offensive or unprofessional.

    2. Re: Heat by jd · · Score: 1

      Badly designed code, comment and corrective action.

      Good code should have contracts that prevent breakage from (ideally) compiling or, at worst, passing absolutely any of the tests in the test harness you've got rigged to run on code checked in to the repository.

      Good comments should explain what is done, not simply justify it. Code reviews should validate that future changes to the code do not invalidate the description.

      The corrective action for checking in broken code, regardless of the nature of the breakage, should involve said coder discovering what the U.S. military mean by being taken for a helicopter ride.

      Then you don't have to worry.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    3. Re: Heat by jd · · Score: 1

      And their code won't compile, no matter what they do.

      Eventually, they'll give up and go back to reading "Fly Fishing" by J. R. Hartley.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    4. Re:Heat by AmiMoJo · · Score: 1

      I always thought the "increase this counter every time you try to improve this and fail" comment was more effective for keeping people away from tricky code. I normally start at 7.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    5. Re:Heat by c · · Score: 2

      I've used some pretty harsh language in the context of compiler bugs.

      Spending days to discover that adding "assert(sizeof(char)==1);" is needed to force sizeof(char) to be 1 is worthy of a good cathartic vent, IMHO.

      --
      Log in or piss off.
  9. 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.

    1. Re: Changing the word won't make it so. by Cmdln+Daco · · Score: 1

      A plumber, Thomas Crapper, invented several key features of the modern flush toilet, which is how the word crap got it's meaning.

    2. Re: Changing the word won't make it so. by CrashNBrn · · Score: 1

      https://www.snopes.com/fact-check/thomas-crapper/

      ...
      Thomas Crapper took out nine plumbing patents between 1881 and 1896, but none of these patents was for the “valveless water-waste preventer” he is often credited with having invented. The first patent for a siphonic flush was taken out by Joseph Adamson in 1853, eight years before Crapper started his plumbing business. Many types of siphonic systems were patented in the 1880s, but none by a Crapper until George Crapper, Thomas’ nephew, was awarded an 1897 patent for “improvements in or relating to automatic syphon flushing tanks.” Crapper may have sold or installed water closets, but he didn’t have much to do with their development.

      Alexander Cummings is generally credited with inventing (or, at least, patenting) the first flush mechanism in 1775 (more than 50 years before Crapper was born), and plumbers Joseph Bramah and Thomas Twyford further developed the technology with improvements such as the float-and-valve system. Thomas Crapper, said an article in Plumbing and Mechanical Magazine, “should best be remembered as a merchant of plumbing products, a terrific salesman and advertising genius.”

      A related legend has it that U.S. soldiers stationed in England during World War I (some of whom had little or no experience with indoor plumbing) saw toilets marked with the name ‘CRAPPER’ and brought the word home as a synonym for ‘toilet’ or ‘bathroom.’ Although the word ‘crap’ (used in a scatological sense) antedates Thomas Crapper and is therefore not derived from his name, the origins of ‘crapper’ as a synonym for ‘toilet’ are unknown, other than that it is a particularly American term whose earliest print citings come from the 1930s.

    3. Re: Changing the word won't make it so. by jd · · Score: 1

      Urban legend, long since... dismissed.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    4. Re: Changing the word won't make it so. by astrofurter · · Score: 1

      Thank you, Dr Pedant, for that learned and insightful commentary.

  10. Why are the swear words there? by ameline · · Score: 3, Funny

    Perhaps it might be a good idea to figure out (and fix) the underlying reasons prompting developers to swear in comments.

    As an aside, One late evening, I once constructed an sql query to look for a variety of swear words in the bug database used at Alias (before Autodesk bought us) -- Amon several, one stood out. It was originally opened by a customer (working in New Zealand on some small films made there -- something about a ring or whatever). It was epic in its use of invective. It tore a strip off of the software and the cretins who had written it (myself included, but not specifically named). The author had been hired and was working at Alias at the time of my query (this was a few years later) (Hi Dave :-) ). We had some fun passing the link to the bug report around.

    --
    Ian Ameline
    1. Re:Why are the swear words there? by Chelloveck · · Score: 1

      Perhaps it might be a good idea to figure out (and fix) the underlying reasons prompting developers to swear in comments.

      And sometimes the underlying reasons are dictated by product management. Like the ridiculous feature they required a whole alternative firmware build for. Ah, such fond memories of #ifdef CLUSTERFUCK.

      --
      Chelloveck
      I give up on debugging. From now on, SIGSEGV is a feature.
    2. Re:Why are the swear words there? by HornWumpus · · Score: 1

      We know at least 6 ways to spell it! You just lack emagination.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
  11. Grow the fuck up by Mike · · Score: 1

    Jesus!

    1. Re:Grow the fuck up by mark-t · · Score: 1

      I understand your point, but swearing is still considered immature and unprofessional. Honestly, it's surprising that this kind of stuff got past code review, let alone making it into a permanent public repository.

    2. Re:Grow the fuck up by mark-t · · Score: 1

      Only in the opinion of people who don't actually have a clue how to act like adults.

    3. Re:Grow the fuck up by goose-incarnated · · Score: 1

      I understand your point, but swearing is still considered immature and unprofessional.

      Is it more or less immature than performing deep searches for things that might offend you?

      --
      I'm a minority race. Save your vitriol for white people.
    4. Re:Grow the fuck up by HornWumpus · · Score: 1

      There are people who are professional and people who act professional.

      You are the fucking second kind.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    5. Re:Grow the fuck up by mark-t · · Score: 1
      That was my point...

      I didn't say that a person was *not* a professional if they used swear words, I suggested that swearing is not typically considered to be professional *behavior*... as in how a person acts around others.

  12. So: that is English swear words dealed with ... by Alain+Williams · · Score: 2, Insightful

    is someone now going to waste their time checking for variable names, words in comments, ... that just happen to be a swear word in French, German, ... and by transliteration Hindi, Chinese, ... ?

    1. Re:So: that is English swear words dealed with ... by Bite+The+Pillow · · Score: 3, Informative

      No.

      Unless you submit a bug report to do so, which will be closed as not enough information, so still no.

      I bet you were proud of this comment. Stop it. You're not helping.

    2. Re:So: that is English swear words dealed with ... by AmiMoJo · · Score: 2

      Does Chinese even have swear words? Japanese doesn't, not really. Even on kids shows they say things like "kuso" (shit) because it's seen as impolite but the concept of "words that simply should not be uttered even though they mean the same as other words that are impolite but not swear words" doesn't exist.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    3. Re:So: that is English swear words dealed with ... by HornWumpus · · Score: 1

      'Du leah lo mo' means 'hello old friend'. Say it to your Chinese associates and coworkers.

      That Chinese has no swear words in an oft repeated lie.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
  13. Correction: a proper rewording of the rot... by Texmaize · · Score: 1

    To some life forms with a certain point of view, civil society is developing a preference for the non-threading, emotional positive form of communication that some but not all refer to as NewSpeak. Due to misogynist, patriarchal, and racial bias of European based civilization, no correct thinking person would read the heteronormative propaganda that some maladjusted life forms would self-proclaim as classics, wrongly implying they had more, not equal value, to the works of other races, cultures, or pronouncement by any person. In doing so, these misogynist, patriarchal, racist individuals hatefully believe that ev***, I mean non-normative points of view, may become prevalent.

    --
    "Liberalism is a very noble idea, currently controlled by some very bad people. Be sure you do not get the two confused.
  14. Open Source by JBMcB · · Score: 1

    It was an old open source project in the late 90's. I could probably dig it up, if it's still around and the repo goes back that far..

    --
    My Other Computer Is A Data General Nova III.
  15. Virtuous by jader3rd · · Score: 1

    When you self proclaim to be virtuous (ie open source is more cirtuous than proprietary) you will eventually attract people who consider themselves to be virtuous. This is a consequence of that.

    1. Re:Virtuous by djinn6 · · Score: 1

      Free software is actually not as virtuous in the political and moral sense. Businesses can be pressured to stop servicing bad people, but free software can be used by everyone.

  16. 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
  17. Case by case by JBMcB · · Score: 2

    I think they should be evaluated on a case by case basis. If for some reason the devs on a project keep messing with the magic number assigned to a file type, a well placed comment cussing them out to prevent that behavior is probably called for. Cussing someone out for a dumb mistake in the code is probably not warranted and should be reverted.

    --
    My Other Computer Is A Data General Nova III.
  18. Professionally? by bill_mcgonigle · · Score: 1

    Does this reporter have any evidence of people using the source of OpenJDK and being somehow unable to cope with the comments or otherwise having problems because of the language?

    It sounds to me like he's making shit up.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:Professionally? by cascadingstylesheet · · Score: 1

      Does this reporter have any evidence of people using the source of OpenJDK and being somehow unable to cope with the comments or otherwise having problems because of the language?

      It sounds to me like he's making shit up.

      It's not about being "unable to cope".

      All words are just arbitrary sounds that convey meaning. So what? Part of the meaning that offensive words convey is offensive meaning. They are literally intended to give offense; that's their meaning. Which is not appropriate in professional settings.

      There's nothing superior about not knowing or caring (or pretending not to know or care) about the meanings of words.

  19. "Too many"? by nagora · · Score: 1

    What is the sufficient amount?

    Here's a tip: do something about something that matters and stick your moronic childish worries about some words up your ass.

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  20. Common in all code bases by 140Mandak262Jamuna · · Score: 1
    One of our developers used a couple of very off color limericks as static strings to test some of his functions in our string utilities library. Well, he forgot to take it out before committing them, and it ended up in code, and some customer ran strings on it ...

    Another developer left in ShowError("Fuck! Got null again!",true/*=fatal*/) in shipping code.

    Another one had a long rant denouncing Osama Bin Laden as a static string, unused but visible in strings.

    It happens a lot.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  21. 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?

    1. Re: Bidirectionality abuse (5:erocS) by illiac_1962 · · Score: 1

      I hear the developers are to appear before the house for questioning.

    2. Re:Bidirectionality abuse (5:erocS) by iampiti · · Score: 1

      Couldn't that just be solved with whitelisting? It's not an ideal solution but if you just whitelist the most common unicode characters and disallow everything else the situation would be better than just allowing legacy encodings

    3. Re:Bidirectionality abuse (5:erocS) by Waccoon · · Score: 1

      Well, at the very least they could implement a filtering hack so apostrophes are no longer broken, which is the most common UTF-8 problem I see around here. A partial solution would be better than nothing.

    4. Re:Bidirectionality abuse (5:erocS) by tepples · · Score: 1

      just whitelist the most common unicode characters and disallow everything else

      Slashdot does exactly this. You disagree with its administrators on which numeric character entities to allow and which to disallow.

    5. Re:Bidirectionality abuse (5:erocS) by iampiti · · Score: 1

      I didn't know. Thanks

  22. I've used JDK by PPH · · Score: 1

    In my opinion, there aren't enough.

    --
    Have gnu, will travel.
  23. Parents Television Council by tepples · · Score: 3, Insightful

    religion doesn't prohibit others from swearing. It only prohibits the religious person themselves from swearing.

    Until the religious people set up organizations like Parents Television Council that lobby governments to prohibit swearing.

  24. Slightly better than what you and I did by raymorris · · Score: 1

    If someone went on a tirade cussing out the developers for the occasional profanity, and demanding everyone else change their behavior, I would tell them to fuck off. From what I can tell, they do didn't have a freak out, they just did a pull request to clean things up.

    > I'd think that maybe they could devote their debugging efforts to more annoying bugs...

    While I don't disagree, I also note that their work is slightly more useful than what you and I contributed to OpenJDK.

    If this person wants to remove the F bombs to make it more "professional", okay - doesn't hurt me. Go ahead and clean it up if you want to.

  25. If you don't like comments... by Glasswire · · Score: 1

    ..or code submitted, feel free to provide "better" submissions with cleaner code or cleaner comments and if people like your version better, it gets in. This is Open Source, no one should be allowed to push out content (incl comments) the project agrees is good without providing a superior submission. Besides this criticism totally ignores the possibility that the thing being described was not so bad that profanity was the most accurate description.

  26. Cultural hegemony by pegdhcp · · Score: 1

    If these snow flakes are that sensitive for perceived insults, I demand all references to "problem" to be removed from OpenJDK. See "problem" translates to my native language as "sknt", which is written as "sikinti" when ASCII used. "Sikinti" in turn can be used in several different contexts those are related to "dick", "fuck" and "fucking". OTOH I am afraid we can actually find some morons who would take my complaint above seriously and try to "correct" this issue. My apologies in advance for any inconvenience that might cause.

  27. Keep it clean, keep it simple. by westlake · · Score: 1

    Mark Twain had to trash the first print run of Huckleberry Finn because an engraver made a subtle pornographic change in an illustration. I doubt he cared whether this off-color joke was ever meant to become public --- as an editor and publisher he had to answer for it. Think about who will be reading your comments and whether they are actually useful.

    1. Re:Keep it clean, keep it simple. by bongey · · Score: 1

      Google page 283 huckleberry finn if you want to read the story. The rare versions of the book are works > 10k.

  28. Not enough blasphemy by OrangeTide · · Score: 1

    For religious reasons I insist source code contains a significant amount of blasphemy. Time to open a bug.

    --
    “Common sense is not so common.” — Voltaire
  29. Re: Dear Snoflakes, by jd · · Score: 1

    Mankind: zombie process

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  30. Java should probably be deleted by jd · · Score: 1

    It doesn't meet the original design criteria, it's unclear it meets the current one either, it's abysmally slow, it encourages bad programming and it causes profuse profanities.

    So it's still better than C#, but really isn't fit for any kind of professional setting.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  31. Usually just one or two devs. by shess · · Score: 1

    In my experience, swears in comments are like swears in real life - usually 90% of the f-bombs in a given group are one or two people. It's not that the other people are so prim and proper that they won't swear, it's that they only swear when it's called for. But there'll be that one person who has to whip out fuck for as an adjective for every minor ailment in their life.

    [Of course, it's different in groups where 90% of the sentences spoken contain a swear word. I haven't often been in such groups since I left the farm.]

  32. What a fucking snowflake :] by najajomo · · Score: 1

    Adam Farley is a fucking snowflake and has no sense of humor :]

  33. WTF by dos1 · · Score: 2

    This is such a non-news. There wasn't even any controversy inside the project. Just a patch, short discussion, resolution, like many others that happen in many different projects each day. How is this newsworthy in any way?

  34. fuck them by Tom · · Score: 1

    I've written tens a couple hundred thousand lines of code in my life.

    Sometimes, "fuck" is the exact word that expresses things correctly, precisely and honestly. Didn't they teach you in CS class to write good documentation? There's stuff out there that cannot be captured any more perfect than writing "fuck".

    I'm all for maturity and professionalism. And when I get a piece of code from someone else and I need to fix it or maintain it or extend it, I don't want it white-washed to conform to someones idea of political correctness. If dealing with this particular piece is a case of fuck, then it is a piece of fuck and I want to know that so I can approach it properly, not thinking "ah, there's a small bit of complication here, no biggie".

    So fuck them and their attitude. Comments are there to transport important information about the code. They aren't campaign speeches or scientific articles. They aren't job descriptions or diplomatic messages to foreign countries. If the author of the code put "fuck" in the comments, that transports important information to me about the code.

    --
    Assorted stuff I do sometimes: Lemuria.org
  35. Re:You're rotten by gweihir · · Score: 1

    JRR Tolkien was a Nazi? You seem to be confused...

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  36. What is the point? by thsths · · Score: 1

    Even if "crap" and "damn" are not swear words, I fail to imagine a situation where they are appropriate in a comment or a variable name (unless you are building a bad language filter, of course).

  37. Well by RuiFRibeiro · · Score: 1

    What prevents us opening now a bug it has too little swear words? Several people can play that game.

  38. Comments in code by brantondaveperson · · Score: 1

    Comments in code are there for a specific purpose. They exist to explain to you, the reader of the code, the intention, functionality and side-effects of the code. Since code cannot fuck, there is no need for the word "fuck" to be found, spread liberally or otherwise, in source code comments.

    Grow up, learn to use the English language properly, and learn to express yourself concisely and clearly in the comments in your code. At best, a "fuck" in the comments is a waste of space. The comments aren't there to get something of your chest, they're there to explain.

    At some point in the future, some of us might be writing firmware for sex robots. At that point, we can have this conversation again.

  39. Q: What language do all programmers know? by brendan.robert · · Score: 1

    A: Profanity.

  40. Real problem by Cro+Magnon · · Score: 1

    I'm less concerned with swearing in the code than I am with code that makes the users swear.

    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.