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


281 comments

  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 Anonymous Coward · · Score: 0

      What is your definition of annoying?

    2. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Me? Well, the most extremely annoying thing is when someone creates so many C macros that you find you canâ(TM)t type any actual code because it gets turned into something else. I guess it is funny to make a macro for printf that does something else but why would anyone do that other than as a prank?

    3. 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
    4. Re:Well, for an expansive definition of "bug" by gweihir · · Score: 0, Troll

      Naa, the SJW scum think form is much, much more important than function. Pretty much the definition of fundamental incompetence in any tech field.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    5. 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.

    6. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Simple. How much do you even care and how far you wanna take these kinds of crusades. Go from there.

    7. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      I ran a report that told me how many f bombs were in the code. I did not include the code I wrote to make the report, well I included the counts in the report but not the code itself. Anyway this is a leading article. What is the obvious question we should be asking about this?

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

      Is this tech noir?

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

    11. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0, Offtopic

      You should look at it the other way around.

      Why doesn't any other platform have this issue?

      Shouldn't thr "smart quotes" understand that it's a standard apostrophe?

    12. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Is that what that is in a posting?! I thought it was some sorta Millennial trademark thingie "canâ".

      Anyway, for those complaining about C macros have never seen the hell of terrible C++ code
      (98% of what's our there). I worked at a place where some clown (no longer there) though it
      was cute to write and entire program with a macro as the entry point (trying to hide main()).

      I had to make a change to that application. I simply used gcc -E to see where to make the change.
      Easy-peasy. Yeah, there's probably some bad C code out there as well, if you look hard enough.

      C macros, properly written, can really help keep a code base clean. I use them for the malloc()
      et. al. group of functions - all of the error checking / reporting is hidden 'cause it's not necessary
      to always see it. They're also a good way to kill the fat-finger error with repeated (complicated)
      calculations - if you screw up the macro nothing should / will work in all of the places it's used.
      But if you discretely code each identical location, a typo will be tough to catch. This sorta defensive
      programming isn't taught anymore - it's all about pretty and shinny.

      CAP === 'busied'

    13. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Not using a dictionary

    14. Re:Well, for an expansive definition of "bug" by fodder69 · · Score: 0

      Lol, surprised it took until the 5th comment for the basement dwelling MRAs to come out.

    15. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0, Insightful

      Ah yes, when I think of who would be most likely to be offended by swear words, my mind also totally ignores the possibility of religious people.

      Religion is for stupid sheep.

      Caring about what religious people are offended by is for idiots.

      Make sure you update your tiny little brain to reflect these facts.

    16. 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
    17. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Probably because whenever a particular topic comes up, it is the loudest groups of people who get the attention. Which in this case, would be SJWs.

    18. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Another thing to think about is that - while stupid like you said - religion doesn't prohibit others from swearing. It only prohibits the religious person themselves from swearing. Those folks seem to think that they get a license to not have to see things that they themselves aren't allowed to do - but that isn't how it is supposed to work.

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

    20. Re:Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Hey - that SJW should be happy we're not in France where 23,633 words
      are consider taboo in that language (22,002 if you're a French-Canadian).

      CAP == 'interval'

    21. Re:Well, for an expansive definition of "bug" by NicknameUnavailable · · Score: 0, Troll

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

      Or you know, just stop making Java, it's well beyond the point of being shit at this point. But I guess that's how it works, something gets associated with being shit, has words describing it as shit, then seeks to outlaw the words describing it rather than change itself.

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

    23. 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.
    24. Re: Well, for an expansive definition of "bug" by Dunbal · · Score: 0

      That depends on the religion. Religions that have gone through an enlightenment and realize that the "road to salvation" is an individual issue have people who don't care what you do - they worry about their own personal conduct. However in some more primitive religions (islam) they care very much about what YOU do or say, and if you do or say the wrong thing you are subject to penalties. In Pakistan blasphemy still carries the death penalty. Go ahead and swear...

      --
      Seven puppies were harmed during the making of this post.
    25. 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."
    26. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Well he did submit a patch... Also, for all of those complaining about the SJWs further down... Its ome thing to I have swear words in commemts when you can reasonably expect that it it will be private. But having them in a large public one is just un-professional...

    27. Re:Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      The poster / protestor of the "bug" report should be blocked from ever submitting any code anywhere ever again. Let us now go and mandate all variables be changed from their useful, clue-giving names to f-bomb-001, f-bomb-002, etc. :)
      Kill the PCism monster!

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

    29. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      They're also a good way to kill the fat-finger error with repeated (complicated)
      calculations - if you screw up the macro nothing should / will work in all of the places it's used.

      Inline functions would be a better way to deal with this when possible, imho. Just as fast without the possibility of weird side effects that comes along with using macros.

    30. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      I relate to that, but the problem is still a lack of guides or a proper Design, macros should only be used for trivial code that won't require to debug or are easy to diagnose.

      And Not only swearing inside of Code, I once found an irrelevant but very amusing story inside a class documentaciÃn, distracting and irrelevant, but I laughed a lot and left it there.

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

    32. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      If you are surprised at Slashdot incompetence after all this time, that's on you.

    33. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      That single developer didn't do jack shit without other people finding the bugs for him.

      And then said single developer fucked those that were trying to help.

      You want to talk belligerence? Michael Casadevall is one of the most belligerent people on this internet.

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

      ... or drink water from the wrong cup.

    35. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      If every other platform jumped off a bridge...feel free to join them. I laud /. for not doing so. Fuck unicode.

    36. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      FUCK! There are too many fucking swear words in this bitch! Fucking fix these mother fucking bugs! This is professional fucking code! No fucking swearing in our code! Also cunt, shit, ass.

    37. Re:Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      Bug: 203102303

      Description: Annoying PC developer doesn't know how to fucking shut the hell up.

      Severity: Critical Show Stopper

      Real Resolution: WONTFIXBECAUSESCARED

      Desired Resolution: RESOLVEDOUTBACK

    38. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      The loudest group of people, by far, are people like you who throw tantrums about every little dumb thing.

      Does it matter if someone made a patch that removed the word "fuck"? No

      But are you going to bitch and whine about it? Yeah, for fucking days. You're going to just have a fucking aneurysm over someone taking time out of their own day to change wording in a project.

      But it's totally the " SJW" people that are sensitive idiots, right? Can't be you. No way.

    39. Re: Well, for an expansive definition of "bug" by Anonymous Coward · · Score: 0

      God damn son! Preach! With views like that it's clear you are one tough-ass hard working motherfucker.

    40. 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'
    41. 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.
    42. 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. damn and crap by Anonymous Coward · · Score: 0

    damn and crap do people have nothing better to do....

  3. 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 Anonymous Coward · · Score: 0

      Because people read the entirety of the source code before choosing to use OpenJDK? 99.99% of people will have never known these swear words existed since it has zero bearing on anything.

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

    4. 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."
    5. 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)
    6. Re:Yeah ... by Anonymous Coward · · Score: 0

      Bitches obviously never even sniffed a punch card and think Prolog is a name of a magic fairy from NULLnia. A real programmer knows how to swear better than a sailor out of a necessity. It makes pain go away... That or self mutilation.

    7. 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
    8. 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."
    9. Re:Yeah ... by Anonymous Coward · · Score: 0

      I was slumming around the Houston Chronicle's comment section when there was talk of a "robot brothel" opening up.

      The Democrat mayor and much of the City Council raised some objections and this means that many the right-wing regulars there were all for it and used it as an issue to criticize Democrats.

      Basically if the Democrats are against something a certain segment of the right will automatically embrace it.

    10. Re: Yeah ... by Anonymous Coward · · Score: 0

      Yeah, them being there had zero bearing on anything. That means removing them also has zero bearing on anything.

      Yet here you are, mad as hell about it. The problem is you, buddy. Learn some damn introspection

    11. Re: Yeah ... by astrofurter · · Score: 1

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

    12. Re: Yeah ... by Anonymous Coward · · Score: 0

      If you're not "mad" about it, you don't care and it won't be changed.

      If you're "concerned", or whatever fucking euphemism, then it will s/mad right onto your parent.

      The point being that you were an idiot to make Measure of Interest the decisive metric, since that's just a symmetrical dead end.

      If your metric is null impact, your demands bear zero value and it won't be changed.

      It's telling that you think emotion is what should determine this.

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

      Punch cards

    14. Re: Yeah ... by Anonymous Coward · · Score: 0

      Acting "professional" is just being a fake replaceable tool. Real professionalism is in the results. Tools are worried what other people think and are afraid to not act professional because that's all they have going for them. Congrats, you can fit in the with rest of the incapable normies. Just a dog and pony show.

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

      At its most extreme? Bare metal assembly.

  4. 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
    3. Re: Reasonable approach by astrofurter · · Score: 0

      True, hypocrisy is the house of social just-us nazis.

  5. 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 Anonymous Coward · · Score: 0

      I wish everyone knew what you were talking about.

      But guess we better be carefull...NewSpeak a may become a trigger word and it would send people running to the racially clean safe space.

    3. Re: The rot is growing stronger by Anonymous Coward · · Score: 0

      What is this "racially clean" thing you speak of? No straight white males allowed?

      I for one await the day the bugreports claim the source is "not diverse enough" and therefore needs pink wallpaper and comic sans to "be more inclusive". Nevermind that source itself sees no color.* And, of course, pink-on-pink is hell on red/green colorblind people. Mostly males affected, so that's probably not an argument for the "social justice for non-straight wite males only"-bunch.

      * I for one use white on black editor windows exclusively, no colorisation at all. I'm pretty sure that counts as racist and oppressive at the same time, for some. CoC, anyone?

    4. Re: The rot is growing stronger by Anonymous Coward · · Score: 0

      Let us begin the Two Minute Hate.

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

    6. Re:The rot is growing stronger by swillden · · Score: 0

      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.

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

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

      Orwell was wrong*. People want to be shitty to each other and will always find a way to insult people. The notion that communication is alone words that can be controlled is actually absurd. The only thing to truly stop people is for there to be dictators at the top who can murder anyone below them for any reason, real or imagined. If NewSpeak were merely a distraction designed to encumber people to much to actual rebel because they're too busy trying to appear acceptable, then just about any sufficiently complex ritual would fill its place.

      * Strictly speaking, 1984 limited its system of NewSpeak to those politically connected, just like political correctness. One could argue in that regard it succeeded as the media regularly functions like Big Brother to chastise those members who fail to use the "correct" words or in implication use words meant to be neutral pejoratively. The reality is words are used ambiguously precisely to mean different things to different people and Big Brother/media isn't so pervasive to prevent private meetings where people can't open up about their real feelings. Even when scandal does erupt when the truth is known, little often happens as those involved have the inertia to often weather the scandal and move on.

    8. 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.
    9. 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
    10. 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
    11. Re: The rot is growing stronger by Anonymous Coward · · Score: 0

      Sounds like InterCal needs a version 2.0

    12. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      In Slovak, fucked means really.

      So, fucked?

    13. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      Of course nobody reads the classics - they're full of disgusting swear words.

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

    15. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      I read them to learn new swear words.

    16. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      So the system works as required, then.

    17. 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)
    18. 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)
    19. 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.

    20. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      There is more than one religion with 3 coming out of a desert. Only one of these produced the snowflakes you can let melt. The others may ignore your attempts or put on a bunch of explosives and come to you so that you can continue the discussion with the virgins. Did you mean any of these 3 or some other religion? Just wanted to be sure I am agitated about the proper one.

    21. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      In Slovak, fucked means really.

      Naozaj? ;) If you're talking about the vernacular "fakt" (= "fact"), there is a passing resemblance, but that and "fucked" are not phonologically the same.

    22. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      Wait a second - are you telling me there are comments in code?

      No wonder nothing happened when I put a breakpoint on them!

    23. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      That's the thing, to oil, tune and calibrate something properly you might actually need to SHOCK HORROR restrict some aspect of it. A well regulated militia does not mean "everyone should be armed to the teeth", it means a large number of good trusted patriots whom are part of the community should be allowed to own and use guns for the defence of liberty. That does not include every citizen, in fact it is quite a RESTRICTIVE command. Keep in mind the founding fathers also never intended for the US to have a standing army when there was no war on and not to meddle in other countries affairs, so I wouldn't cry too hard about what they wanted vs reality.

    24. 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.
    25. 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?
    26. 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"
    27. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      The vast majority of open source isn't a hobby and hasn't been for a very long time. Its largely done by employees or sponsored.

    28. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      Since you used the term "SJW" I'll assume you're a right winger whether that's a fair assumption or not.

      How would you feel about code littered with comments like: // Whoever wrote this was probably an idiot Nazi just like Donald Trump!!!!

      I suppose you could respond in kind by adding // Whoever wrote that last comment is a fucking Soros-paid socialist. // He's got TDS

      And before you know it your source code is littered with comments that aren't worth reading because they're NOT FUCKING HELPFUL.

      You've got to set some FUCKING standards. People WILL disagree on what those standards should be but when you do you shouldn't be such a snowflake that you can't be civil about it and conform to them.

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

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

    31. 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
    32. 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.
    33. 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
    34. 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'
    35. 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'
    36. 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'
    37. 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'
    38. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      If a compiler reads it in a forest, then discards it as the flag instructed without a sound, can you say the knowledge no longer exists to the compiler?

      (Yes.)

    39. 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"
    40. 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
    41. 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.
    42. Re:The rot is growing stronger by Anonymous Coward · · Score: 0

      In a free society you have to tolerate others just as you want them to tolerate you. When you suggest or advocate murder as a solution, even in jest, what this does is define you and your group more than it has any effect that you might have intended. And you will quickly find yourself alienated from pretty much every other group that had previously tolerated you and your group. Tread carefully.

  6. 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
    2. Re:Next it'll be git commit messages by Anonymous Coward · · Score: 0

      ", as well as javascript, typescript and typeshit."

    3. Re:Next it'll be git commit messages by Anonymous Coward · · Score: 0

      "Fuck this hg shit, I'm converting the repo to git" would be so awesome....

    4. Re:Next it'll be git commit messages by Anonymous Coward · · Score: 0

      Ha, I just realised, git commit messages are golden... they'd have to rebase the entire repo and taint all the time stamps and authors to change those, not to mention cause hell for anyone who had branched for a PR.

    5. Re:Next it'll be git commit messages by Anonymous Coward · · Score: 0

      and Cfagfag.

  7. 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
    2. Re:Kill all the children... by Anonymous Coward · · Score: 0

      My operating systems teach in University was from Kenya and had a very thick accent.

      It was a hilarious day when we got to forking a process, child processes, etc.

      "So you have a program and you need to get more work done. You fork the process and you get a child. If you want to, you can fork the child and make another child. When you are are done forking, then you get the work done, and then when you are done with work you can kill the childs."

      Of course, his accent meant he wasn't saying "FORK".

      But he certainly SAID "FORK" a lot that day. We were almost crying with laughter.

    3. Re:Kill all the children... by Anonymous Coward · · Score: 0

      strike the baby kill the blonde
      is a phrase used in theatrical/film lighting.
      a baby and a blonde are specific types of lights.

    4. Re:Kill all the children... by Anonymous Coward · · Score: 0

      And that was exactly whose fault? No one, that's who. It's a perfectly legitimate way to phase what was done. Where the hell's this gonna end? We can't say parent, child, spawn, kill, execute, etc... Just because somebody somewhere will get butthurt?

    5. Re:Kill all the children... by Anonymous Coward · · Score: 0

      was it killed by a daemon?

  8. 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 Anonymous Coward · · Score: 0

      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.

      The programming language Brain Fuck consists of 8 single-character instructions: plus, minus, greater than, less than, open bracket, close bracket, period, and comma.
      Any other characters are ignored as white space and can be used for padding and indentation.

      This presents a unique combination where the language name contains the word 'fuck', which can consist of instructions to print out 'fuck' on screen in a loop, with white space consisting only of the word 'fuck', used to pad out the actual instructions such that they form a mono-spaced 40 column ascii 'fuck'

      I was bored anyway, so here's a v0.0.1
      https://pastebin.com/raw/11rEBhHB

      The 3x5 font sucks, but hey it compiles and runs!

    2. Re:Challenge Accepted by Anonymous Coward · · Score: 0

      How about... a programming language? Patterned after rust, of course.

      Also do something profane with the intercal please/do/please do rule.

      Source should be relatively simple, so it's easy to bootstrap. The "Let's Build A Compiler" text file series is a good starting point.

      Once it compiles itself, the next steps are to implement an editor, a SCM, and a ticketing system. Oh, and an email client, of course. After that, an X interfacing library and, how about a web browser?

    3. 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.
  9. Dear Snoflakes, by Anonymous Coward · · Score: 0, Insightful

    Please fuck off.

    Sincerely,

    mankind.

    1. 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)
  10. 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: 0

      I'm going to take your word that this is an actual true case. If it is, that's f***ing hysterical. I would think the SERIOUSLY would stop me, but I guess everyone is different. I agree that context is everything, and in this context, it seems appropriate.

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

    3. Re:Heat by Anonymous Coward · · Score: 0

      I had the same experience. I'm not sure if it's still valid but at some point sdl required including sdl.h in the cpp file with main due to some init code, but only on mac. I included sdh.h inside #ifdef __APPLE__. That should be the end of the story, but no.

      What happened is that somebody changed __APPLE__ to WITH_SDL. It still worked fine. Next a third person found it odd as the file was not supposed to interact with sdl and deleted the include. I'm not sure what happened to the comments, but apparently those were gone at this point as well. He tested it on linux and since it didn't result in any problems, he committed it. Nightly builds compiled fine, but then we got reports that the mac port would crash at startup.

      Long story short, the include came back and with some comments about... let's just say the next person to remove it wouldn't win any popularity contests.

      Sometimes you need to use strong language and sometimes it just feels good to do so after having discovered that somebody else broke your code and you had to spend time fixing the mess.

      I still consider it to be a bad design that the mac port and only the mac port of sdl required the header to be included for main, but when using a library rather than creating your own library, you just have to accept such conditions and design your code accordingly.

    4. Re:Heat by Anonymous Coward · · Score: 0

      Now you will have to write DO NOT TOUCH OR I WILL HUG YOU. Could even work

    5. Re: Heat by Anonymous Coward · · Score: 0

      Sounds like a bad comment. If you find something odd or hacky, there should be comments on why the code was written as it was.

      A simple "// macs need this, or crashes on startup" should be enough for the average programmer.

    6. Re: Heat by Anonymous Coward · · Score: 0

      Sounds like a bad comment. If you find something odd or hacky, there should be comments on why the code was written as it was.

      A simple "// macs need this, or crashes on startup" should be enough for the average programmer.

      Apparently that didn't work this time because it says "I'm not sure what happened to the comments, but apparently those were gone at this point as well.".

      I will not completely rule out foul play. I wouldn't be surprised if a linux or windows users broke the mac port intentionally because "Apple is bad". I have seen this with a few open source projects where one person breaks the work of another person due to personal reasons or different point of views. It's rare, but when it happens the real victim is the project itself. The fact that it had comments, which apparently vanished could point in this direction.

      I recently had to kick one person from a project for this reason. At some point I proposed a change. All except one agreed it would be a major improvement. Later this new feature stopped working as intended and guess what: the git log revealed who broke it and "surprisingly" it was the only person against the feature. A week later another feature, which used to work was fixed and once again the git log pointed back to the same person. The same person who was also in this case the only person to oppose the change. It doesn't matter how good people are at what they are doing. You need to kick people who sabotage the work of the other members or the project itself will become broken and die.

    7. 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)
    8. Re:Heat by Anonymous Coward · · Score: 0

      People kept messing with it.

      The people messing with it should have gotten fucked - not the comment.

    9. Re: Heat by Anonymous Coward · · Score: 0

      Then you don't have to worry.

      Yeah you do. There are idiots out there coding that don't read comments. **Escpecially** if those comments are a block of text they have to read for comprehension.

    10. 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)
    11. 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
    12. 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.
  11. use a filter by Anonymous Coward · · Score: 0

    cat *.java | ned_flanders

  12. Un Phoque by Anonymous Coward · · Score: 0

    It's amazing how the French survive having to hear that word every time they visit the sideshows at a cetacean institute.

    Is it the sound that bothers people? I can't imagine the word in the code is being used to insult the complainant or anyone he knows... or hell, even a person in general, so it can't be that. I genuinely don't understand.

    1. Re: Un Phoque by Anonymous Coward · · Score: 0

      Now youâ(TM)re just doing it on purpose

  13. Slow news day? by Anonymous Coward · · Score: 0

    Really, this is worth putting up?

    Ya, I use FFS all the time in my comments. Usually because I'm maintaining code at the time and I have to spend hours figuring out WTF the code is doing and why it was written in such a stupid manner.

    Seriously, it's a valid note for future developers that take over the code base.

    So you can search my code for TODO, XXX and FFS

  14. four f-bombs by Anonymous Coward · · Score: 0

    I use Java extensively at work and I constantly think this as I use it.

  15. 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 Anonymous Coward · · Score: 0

      Hey, watch the swear words! . . . Oh, wait. "crap" is not a swear word. Carry on.

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

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

    4. 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)
    5. Re: Changing the word won't make it so. by astrofurter · · Score: 1

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

  16. 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 Anonymous Coward · · Score: 0

      What?

    2. Re:Why are the swear words there? by Anonymous Coward · · Score: 0

      Because developers are human and humans love swear words. Well, except those damn ass cunts who do nothing but police others because they're fucking tyrants on a power trip .... shit!

    3. Re:Why are the swear words there? by Anonymous Coward · · Score: 0

      >Perhaps it might be a good idea to figure out (and fix) the underlying reasons prompting developers to swear in comments.
      Or just do nothing, because a handful of swears isn't seen as a big deal.
      And maybe *that* is the underlying reason: the visceral power curse words once had has diminished, mainly due to increasing casual use; and a culture that increasingly states that words can't *cause* offense, only that offense can be taken.
      There's ironically a large overlap of people who think that way, but are quite comfortable shutting down other speech, because they're a bunch of nation-wrecking n1gger-loving kikes.

    4. 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.
    5. Re:Why are the swear words there? by Anonymous Coward · · Score: 0

      Impressive... All those words, and you managed to not actually say anything.

    6. Re:Why are the swear words there? by Anonymous Coward · · Score: 0

      For all their flaws, at least most developers would actually know how to spell vocabulary.

      Perhaps if you spent less time denigrating your intellectual superiors, you might achieve something with your pathetic life.

    7. 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'
    8. Re:Why are the swear words there? by Anonymous Coward · · Score: 0

      > Perhaps it might be a good idea to figure out (and fix) the underlying reasons

      Might not be fixable in that sense. /**
      @author Arthur Fuck
      */ // This code is fucking cool!!

      etc.

  17. Grow the fuck up by Mike · · Score: 1

    Jesus!

    1. Re:Grow the fuck up by Anonymous Coward · · Score: 0

      Indeed. The guy didn't encounter a swear word while working on the code, he did a word-search in a million-line codebase in the hope of getting offended.

      I bet you can also find f-bombs in the ASCII dump of some music CDs. Is that guy going to officially complain to record labels about this?

    2. Re:Grow the fuck up by Anonymous Coward · · Score: 0

      Jesus!

      Setting a great example .. cussing twice in a five word post

    3. Re: Grow the fuck up by Anonymous Coward · · Score: 0

      These are uppity managers. Obsessed with swears

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

    5. Re:Grow the fuck up by Anonymous Coward · · Score: 0

      Swearing is only considered immature and unprofessional by people who are themselves immature and unprofessional children in adults' bodies.

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

    7. Re: Grow the fuck up by Anonymous Coward · · Score: 0

      We don't give a fucking anymore.

    8. 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.
    9. 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'
    10. 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.

  18. 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 Anonymous Coward · · Score: 0

      As an example, never use this Xoza phrase in Russia: "Yebo baba".

      It may get you seriously fucked over.

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

    3. Re:So: that is English swear words dealed with ... by Anonymous Coward · · Score: 0

      Swearing in C++? m*llocs to that.

    4. Re:So: that is English swear words dealed with ... by Anonymous Coward · · Score: 0

      If someone names a variable "shit" in French and the variable is not about the "shitting duck" project, then it needs to be changed to a "meaningful name". The worst code is nonsense words.

    5. Re:So: that is English swear words dealed with ... by Anonymous Coward · · Score: 0

      Yes.

    6. 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
    7. 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'
    8. Re:So: that is English swear words dealed with ... by Anonymous Coward · · Score: 0

      My favorite was when I worked for a swedish company. They had a coding standard to put something that was either 'end' or something similar to the end of each function to indicate the end of the function. That word was 'slut'. So at the end of every function was written 'slut'. Many laughs were had by us english speaking folk. The funny part was, even though all the swedes spoke excellent english, the meaning in english never occurred to any of them. It becomes even funnier when the companies official language was english.

  19. 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.
  20. Bug closed: Invalid by Anonymous Coward · · Score: 0

    Note from the developer: Fucking deal with it, you twat!

    1. Re:Bug closed: Invalid by Anonymous Coward · · Score: 0

      Nah, Fucking deal with it, you wanker.

  21. 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.
  22. Hug Off! by Palanthis · · Score: 0

    People getting all bent out of shape about profanity in opensource code comments can go hug themselves...

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

  24. A, Java... by Anonymous Coward · · Score: 0

    you can only bear the pain with swear words and lots of whisky.

  25. Poor management by Anonymous Coward · · Score: 0

    I divide my officers into four groups. There are clever, diligent, stupid, and lazy officers. Usually two characteristics are combined. Some are clever and diligent -- their place is the General Staff. The next lot are stupid and lazy -- they make up 90 percent of every army and are suited to routine duties. Anyone who is both clever and lazy is qualified for the highest leadership duties, because he possesses the intellectual clarity and the composure necessary for difficult decisions. One must beware of anyone who is stupid and diligent -- he must not be entrusted with any responsibility because he will always cause only mischief.

    Kurt von Hammerstein-Equord

    Judging by the amount of busywork recently trying to "professionalize" various open source projects, it looks like we're in trouble.

  26. Fuck. by Anonymous Coward · · Score: 0

    The word is "fuck". There are no bombs in the source code. Do you need someone to hold your peepee when you go weewee or are you a big boy who can use big boy words?

  27. 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
    1. Re:This is exactly why you should try not to swear by Anonymous Coward · · Score: 0

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

      That's precisely the danger with speech police: they end up giving more power to mere words. Want words to be powerless? Overuse them, don't ban them.

    2. Re:This is exactly why you should try not to swear by Anonymous Coward · · Score: 0

      Amusing swearing comments aside, this is what things like cvs or git triggers should be used for to prevent or notify if some code is changed.

      otherwise known as *EXTREMELY FUCKING USEFUL* shit. I kid you not :)

    3. Re:This is exactly why you should try not to swear by Anonymous Coward · · Score: 0

      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.

      Exactly. I was once in a meeting where a very circumspect high-level suit exploded "horse shit" to an outrageous obstructionist bureaucratic absurdity. The room went silent - none had ever heard use an "obscenity" before. It had effect. Had I said that, alas, no one would have noticed. Fuck it, I've squandered my word effectiveness on trivia.

    4. Re:This is exactly why you should try not to swear by Anonymous Coward · · Score: 0

      The reason that comment kept people away is because swearing in code is still relatively uncommon, so it has power.

      Correct.

      So keep the F-bombs out of code, so when the time comes where it is needed, it still works.

      Won't work, because the really needed ones will also be patched out as soon as they are identified.

      Your approach would require the people looking for things like this to also understand the underlying reasoning for *some* of them being there in the first place and to care about such reasoning. Not happening, evidently.

  28. 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.
    1. Re:Case by case by Anonymous Coward · · Score: 0

      If I saw something that said "Don't Fucking Touch This" and I suspected it might be causing problems I'd rather the comment explain WHY I shouldn't touch this.

      How would I know the person who put that there wasn't a FUCKING IDIOT?

  29. Your opinion is a bug. by Anonymous Coward · · Score: 0

    Your opinion is a bug.

  30. 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 Anonymous Coward · · Score: 0

      An analogy might help make your point clear:

      "As OpenJDK pork is served in upscale restaurants, could you please make sure that the OpenJDK pork farm doesn't smell?"

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

  31. Gratitude by Anonymous Coward · · Score: 0

    An entire generation of people should be thankful that this is the level of problems they are faced with.

    It makes me glad that we're so far from 'nasty, brutish and short' at this time in history.

  32. New bug report by Anonymous Coward · · Score: 0

    Adam Farley is so weak-minded that mere words have such a drastic effect on his mental capability.

    Suggested fix: Learn to not give a fuck about words, you soft-minded shit.

  33. "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"
  34. This explains OpenJDK's flaws nicely by Anonymous Coward · · Score: 0

    Spending all this time on fixing "swear words" instead of fixing actual bugs.

    This is why I don't use OpenJDK and its buggy shit in the first place, Adam.

  35. Swear words by Anonymous Coward · · Score: 0

    are by definition words perceived to be offensive. The idea that some fucks sitting around sucking each others dicks (how likely is it that females participated in this stupidity?) think they can arbitrate what is offensive across all of the world's (English speaking) cultures is moronic beyond belief. Since these guys don't think crap is offensive, then they should be required to roll in it thrice daily. What utter pukes.

  36. 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
  37. 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 Anonymous Coward · · Score: 0

      better users!

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

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

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

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

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

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

      I didn't know. Thanks

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

    In my opinion, there aren't enough.

    --
    Have gnu, will travel.
  39. FUUUUCK by Anonymous Coward · · Score: 0

    I thought this was about open jedi knight. Well actually this is good, i don't care about open jdk, but still. This kind of crap is total bullshit.

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

  41. Fix bugs, not comments by Anonymous Coward · · Score: 0

    Assholes.

  42. Comment removed by account_deleted · · Score: 0

    Comment removed based on user account deletion

  43. F-bomb? by Anonymous Coward · · Score: 0

    WTF is an F-bomb?

    1. Re:F-bomb? by Anonymous Coward · · Score: 0

      F is the chemical symbol for fluorine, dumbass.

  44. such a good use of developers' time (NT) by Anonymous Coward · · Score: 0

    such a good use of developers' time

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

    1. Re:Slightly better than what you and I did by rtb61 · · Score: 0

      Why exactly is 'FUCK' more offensive than 'SEXUAL INTERCOURSE', I mean is it evil to use less letters, or are 'F' and 'K' inherently disturbing. I mean how about hump or screw, is hump OK because camels do it and of course banning the word screw would be stupid even when it is the implication in context.

      How about you silly fuckers try to stop taking offence at everything, chill the fuck out, and realise the difference between words and physical actions. You know like I learnt in kindy, sticks and stones may break my bones but names will never hurt me. Instead of the silly crap now, ohh ahh, they said some dirty words, let's get some sticks and stones and break the bones.

      Fuck off with this silly shite already, everyone needs to grow the fuck up. The artful fun use of words is the artful fun use of words, want to take offence, go right ahead it will just make it even more fun.

      --
      Chaos - everything, everywhere, everywhen
    2. Re:Slightly better than what you and I did by Anonymous Coward · · Score: 0

      I am pretty sure that the 'U' and 'C' are the disturbing letters, since they are the ones that are blanked out when people self sensor themselves in this way F**K.

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

  47. Obviously its time by Anonymous Coward · · Score: 0

    Its time for a programming language where every keyword is a swear word.

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

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

  50. 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
  51. 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)
  52. 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.]

  53. Re: This is exactly why you should try not to swea by Anonymous Coward · · Score: 0

    They âoeloseâ effect, not loose.

    When you use the wrong word, it kind of loses the effect, too.

  54. Re:Smash Face. by Anonymous Coward · · Score: 0

    Bzzt! Thank you for playing! You assume much! But, that just makes and ASS out of U, but, not ME! Dumbass! Go back to your mother's basement you cowardly pedophile and stop diddling children. If I catch you fucking around with children again, I'll cave your fucking skull in with a hammer you worthless prick. Yes, I am Gerald Edward Butler (real name). I am not a coward squealing in the corner like your faggoty, SJW, MAGA, child molesting, fuck-tard piece of shit that you are.

    the pathetic living punchline that calls himself gerald butler

  55. Clean up.. by Anonymous Coward · · Score: 0

    Can they remove the shit code at the same time they remove the word??

  56. You're rotten by Anonymous Coward · · Score: 0

    Says the motherfucker with a goddamned nazi username. Fuck right outta here.

    1. 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.
  57. side effect of "inclusive" culture by Anonymous Coward · · Score: 0

    when you start hiring snowflakes offended by everything they will soon find time to derail engineering frivolously to gain attention.

    sadly companies like Google, Microsoft and Facebook are establishing a precedent in hiring these kinds of people and it doesn't look like it is going to improve anytime soon.

    for all the marketing about their positive impact little is mentioned about their negative impact on the engineers who are there because they just care about the engineering and not all the emotive garbage these people bring.

  58. Which is it? by Anonymous Coward · · Score: 0

    Twelve or many?

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

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

  60. I would not like to work with Adam Farley by Anonymous Coward · · Score: 0

    Condolences to all of Adam Farley's coworkers who have to endure his frivolous bullshit on an ongoing basis.

  61. Two words; Christian Edition! by Anonymous Coward · · Score: 0

    Fork it!

  62. Pussies by Anonymous Coward · · Score: 0

    Fucking snowflakes.

  63. 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?

  64. I once got in trouble for naming a file "shit" by Anonymous Coward · · Score: 0

    It was just a scratch file in my own home directory...well, it was a shared support home directory but I was almost always the one doing support for this customer.

    But it was on their machine and one day one of their people noticed it.. Stuff Here Is Temporary (shit). I'm not sure how big of a stink the complainer made but it was a big customer who didn't like it.

    About 6 months later I got a job with one of their other customers and my first project was to upgrade them to the latest version of my old employer's software which meant re-integrating all of my new employer's customizations. So, they sent me a tape with an official version of the latest base code and there in one of the directories was a file called "shit" and it wasn't mine. I think I know who put it there, but I didn't think it was worth making a a fuss over. It didn't seem to be an important file.

    Another time a co-worker was chided for writing a simple script called "shat". It was basically an enhanced version of what that did do something useful although I can't remember what exactly now.

    And apparently naming servers things like "ecoli" and "salmonella" is frowned upon when you work for a meat company.

  65. 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
  66. 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).

  67. Well by RuiFRibeiro · · Score: 1

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

  68. Re: This is exactly why you should try not to swea by Anonymous Coward · · Score: 0

    They "lose" effect, not âoeloseâ.

    When you fuck up while correcting someone, it kind of loses the effect too.

  69. c code as example by Anonymous Coward · · Score: 0

    #include "pants.h"

    enum {
      FUCK = 0,
        SHIT,
        CUNT,
        ASS,
        PUSSY,
        MOTHERFUCKER,
        WHORE
    };

    int cocksucking = FUCK;

    void some_fucking_function_run_in_retarded_thread (const char *unclefucker)
    {
            while(cocksucking == FUCK){
                int rectal = check_anal_thermo();
                if(rectal > MOTHERFUCKER) printf("Your ass is on fire %s\n", unclefucker);
    }

    void stop_dicking_aound()
    {
        cocksucking = SHIT;
    }

    1. Re:c code as example by Anonymous Coward · · Score: 0

      How do you cumpile this?

  70. Swearing = use of God's name in vain by Anonymous Coward · · Score: 0

    Swearing = use of God's name in vain - PROFANITY = the word they ought to use instead. OpenSORES & PROFANITY = deserved in https://www.bleepingcomputer.c... AND MORESO in https://securityintelligence.c...

    * ... & IDIOTS around here "DEMAND" I open my code to the world?

    Bwaahahahaha - Look up Google EFast & tell me another one (ontop of those 2 evidences of OPENSores being BUSHWHACKED).

    REPOST vs. BOGUS DOWNMOD WHEN I POSTED IT BEFORE https://developers.slashdot.or...

    APK

    P.S.=> The DOUBLE-EDGED RAZOR of OpenSORES is all that, with proof... apk

  71. Fuck Piss Dick Shit Cock Turd by Anonymous Coward · · Score: 0

    ..and McGillicutty

  72. Re:Swearing = use of God's name in vain by Anonymous Coward · · Score: 0

    By definition, your repost is redundant and also belongs at -1. Your original post was off-topic, and also deserved its moderation. "Open sores" was a term criticized by Slashdot trolls many years ago to mock open source software. You've provided zero evidence of your previous allegations that trolls have threatened to make malicious versions of your software. You've provided zero evidence that open source software is inherently vulnerable or should be untrusted.

    As for the "demands" to release your source code, it's because your numerous vendettas, bigoted comments, and generally unstable behavior suggest that your software cannot be trusted. Your work is not trusted because of your refusal to sign your binaries and demonstrate reproducible builds as part of the source code audits. You're correct that you aren't obliged to release the source code to your software. However, your actions provide ample reason for people to not run your software without the source being released.

    And yes, although swearing and cursing have alternate meanings, they are also synonymous with the use of profanity. Your comment about that was not helpful. While using the word "fuck" in source code comments might be unprofessional, someone also needs thicker skin if they were offended by the use of "damn" or "crap" in the code. That's the real issue here, that thin-skinned people (like you) get bent out of shame about things that aren't important.

    Grow up. And stop spamming.

  73. Translated to native "trollspeek" by Anonymous Coward · · Score: 0

    See subject & ".1- ta sgnoleb osla dna tnadnuder si tsoper ruoy ,noitinifed yB" - by JEALOUS "Lil' Jowie the DO-NOTHING "ne'er-do-well" who STALKS me by UNIDENTIFIABLE anonymous on Sunday December 16, 2018 @06:35PM (#57814128)

    LMAO!

    * You can BLAME YOURSELF for my RESURRECTING an old python script of mine per https://developers.slashdot.or...

    APK

    P.S.=> As long as you STALK me by UNIDENTIFIABLE anonymous posts, I'll continue to DEFY you (especially vs. BOGUS abused downmods you do) as I like REPOSTING vs. bogus downmods - & there is NOTHING you can DO about it, powerless do-NOTHING "ne'er-do-well" chickenshit scared of ME little WEEZIL you are... apk

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

    1. Re:Comments in code by Anonymous Coward · · Score: 0

      No fuck you. If you think that a word like fuck needs to be banned then you are the childish one.

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

    A: Profanity.

  76. 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.
  77. What is the correct number of swear words? by Anonymous Coward · · Score: 0

    There are no words better with which to opine on a subject than a swear word or two. I would have asked the bug reporter how many swear words they felt was just right.