This is why we have super-a r s bound to (insert-random-string)



  • Found while grepping around some testfiles.


    www/api/07_submit_metadata.t:# $multiple_upload_metadata->{$upload_id}->{description} = 'Once upon a time there lived a beautiful princess named Iris Princess Iris spent her days riding her golden horse through the lush forests and deep gorges of her fathers vast kingdom One day Iris was swimming in a pool beneath a waterfall Her steed the fish in the stream and the birds in the trees were her only company But on that day a noisy old hag emerged from the forest and chose to make herself an unwelcome guest amidst this quiet company Beautiful girl the hag shouted at Iris from the shore Iris brushed her long blonde hair away from her face and turned to look at the old woman Go on respond in kind the woman said Say what you are thinking Or do not say it Either will do just fine as you are thinking so loud I can hear it from here thinking that I am an ugly old woman';



  • Don't stop there, what happens next? Heavy granny/jailbait strapon action?



  • So your coworkers write fairy tales?  Look for more stuff and offer to do some editing for them.



  • "Oh Mummy, stop frightening the horses."



  •  TRWTF is not having any punctuation.


  • Trolleybus Mechanic

    @Severity One said:

     TRWTF is not having any punctuation.

     

    The evil witch stole it all.

     



  • @Lorne Kates said:

    @Severity One said:

     TRWTF is not having any punctuation

     

    The evil witch stole it all

     

    This is unrelated but I have a pet peeve against people who prefer to omit the semicolons on their javascript and I dont even have a dedicated key on my keyboard

     



  • @Zecc said:

    @Lorne Kates said:

    @Severity One said:

     TRWTF is not having any punctuation

     

    The evil witch stole it all

     

    This is unrelated but I have a pet peeve against people who prefer to omit the semicolons on their javascript and I dont even have a dedicated key on my keyboard

     


    Well then, shit.



  • @Ben L. said:

    Well then, shit.
    My sarcasm is running low lately, so I'll just leave it at this:

    If that language doesn't use line terminators (like say Python or Lua or so many others) then that's fine. But it's not JavaScript.



  •  A classic: http://www.macs.hw.ac.uk/~pjbk/humour/polynomial.html  Known to be embedded as comments as early as the mid 1970's.



  • @Zecc said:

    This is unrelated but I have a pet peeve against people who prefer to omit the semicolons on their javascript and I dont even have a dedicated key on my keyboard
    I did some reading on keyboard layouts and I'm going to give Slovak programmers a break.

    Incidently, I assume most US and UK programmers don't give AltGr much credit (if they even have one), but I wouldn't be able to type [ ], { } and @ without it. I also need shift to get to /.

    As I understand other European keyboard layouts are similar, and some even have [ ] and { } away from AltGr, making them unconfortable to type with a single hand, if you're into that.

    I shudder to think of AZERTY typers having to use shift to get digits.

    But I guess there are much worse keyboard layouts.


  • Considered Harmful

    @Zecc said:

    @Ben L. said:

    Well then, shit.
    My sarcasm is running low lately, so I'll just leave it at this:

    If that language doesn't use line terminators (like say Python or Lua or so many others) then that's fine. But it's not JavaScript.


    Go does use semicolons, but, like Javascript, it has automatic semicolon insertion functionality. Unlike Javascript, it has a formatter that is the de facto "correct format" to write Go in. That formatter will remove unnecessary semicolons in favor of ASI.


  • Discourse touched me in a no-no place

    @Zecc said:

    Incidently, I assume most US and UK programmers don't give AltGr much credit (if they even have one), but I wouldn't be able to type [ ], { } and @ without it. I also need shift to get to /.
    I rarely use it for programming, but since I prefer a US keyboard layout to the UK one, I use it to be able to type a £ (AltGr L-) along with all the other things Windows users tend to use obscure Alt#### codes for (° (o o) ™ (tm) ½ (12) ² (^2) ł(l/) etc.)


  • Considered Harmful

    I use the United States Unicode Extended 2 (1, 2, 3, 4) keyboard layout from keyboards.jargon-file.org.



  • @joe.edwards said:

    I use the United States Unicode Extended 2 (1, 2, 3, 4) keyboard layout from keyboards.jargon-file.org.
    Sometimes I feel like typing <font size="4">☠☢☣</font> in comments too.



  • @Zecc said:

    @joe.edwards said:

    I use the United States Unicode Extended 2 (1, 2, 3, 4) keyboard layout from keyboards.jargon-file.org.
    Sometimes I feel like typing <font size="4">☠☢☣</font> in comments too.


    Small font sizes + complex glyphs = physical headache.

    Especially the skull one, ironically.



  • @joe.edwards said:

    Filed under: I could actually see some benefit in having a "one true code format" as long is I can be the one who decides exactly what that one true code format looks like.

    A "one true code format" would be awesome for every language. Even if it was different per-language.


  • ♿ (Parody)

    @Ben L. said:

    A "one true code format" would be awesome for every language. Even if it was different per-language.

    I'm not a fan of this idea. At least, not in the sense that everything must be formatted this way instead of a guideline. I will often do something other than follow a rule I consider to be part of The One True Format because making an exception makes the code easier to read. But that's generally something about newlines or indentation of long lines.


  • Discourse touched me in a no-no place

    @Ben L. said:

    Small font sizes + complex glyphs = physical headache.

    Especially the skull one, ironically.

    You need a better monitor with denser pixels.


  • Discourse touched me in a no-no place

    @boomzilla said:

    @Ben L. said:
    A "one true code format" would be awesome for every language. Even if it was different per-language.
    I'm not a fan of this idea. At least, not in the sense that everything must be formatted this way instead of a guideline. I will often do something other than follow a rule I consider to be part of The One True Format because making an exception makes the code easier to read. But that's generally something about newlines or indentation of long lines.
    The advantage of "one true format" is that you can auto-format everything before commit to your code repository and that mostly keeps the size of diffs down so that they reflect the structural changes (i.e., the interesting ones). That's a bigger deal than it initially sounds like. (Alas!)



  • Or maybe we need diff tools that ignore formatting.


  • Discourse touched me in a no-no place

    @dkf said:

    The advantage of "one true format" is that you can auto-format everything before commit to your code repository and that mostly keeps the size of diffs down so that they reflect the structural changes
    That can be (and is here) done without requiring the extra step of reformatting the code before it gets committed. It's not an advantage, it's something else that can screw things up if it gets forgotten.




    Think "minus 100 points" and I fail to see how this concept can even reach positive territory.


  • Discourse touched me in a no-no place

    @Zecc said:

    Or maybe we need diff tools that ignore formatting.
    Not too difficult to craft one if you don't mind a bit of scripting:

    • Pull rev1, pipe through script that pretty-prints it and save to $file.rev1
    • Pull rev2, pipe through script that pretty-prints it and save to $file.rev2
    • $DIFF $file.rev1 $file.rev2


      • Of course, if you don't mess around with the formatting beyond what's needed to actually create the diff, then this isn't a problem....


  • @Ben L. said:

    @Zecc said:
    This is unrelated but I have a pet peeve against people who prefer to omit the semicolons on their javascript and I dont even have a dedicated key on my keyboard
    Well then, shit.

    At least Go abends when you do this (Javascript doesn't). Go also abends for any reason whatsoever (didn't use imported package?), but that is beside the point.

     



  • @Faxmachinen said:

    @Ben L. said:

    @Zecc said:
    This is unrelated but I have a pet peeve against people who prefer to omit the semicolons on their javascript and I dont even have a dedicated key on my keyboard

    Well then, shit.

    At least Go abends when you do this (Javascript doesn't). Go also abends for any reason whatsoever (didn't use imported package?), but that is beside the point.

     


    Uh, no it doesn't...


  • Garbage Person

    @joe.edwards said:

    I use the United States Unicode Extended 2 (1, 2, 3, 4) keyboard layout from keyboards.jargon-file.org.
    I like that. Quite a lot, actually. Have used dead-key spanish for a long time, but I'd never considered looking for all the weird characters (some of which I actually use!) on AltGr.


  • Discourse touched me in a no-no place

    @Zecc said:

    Or maybe we need diff tools that ignore formatting.
    Does your SCM use them as part of its implementation, or are they just visual conveniences for you? While the latter is very nice, the former is exceptionally likely as SCMs — especially modern ones — are designed to maintain files perfectly, and not just random approximations to them.



  • @dkf said:

    @Zecc said:
    Or maybe we need diff tools that ignore formatting.
    Does your SCM use them as part of its implementation, or are they just visual conveniences for you? While the latter is very nice, the former is exceptionally likely as SCMs — especially modern ones — are designed to maintain files perfectly, and not just random approximations to them.
    Don't get me wrong. SCMs should definitely not ignore whitespace. Changes are changes.
    Whitespace in some cases is even fundamental. Indentation in Python is an obvious example, but also — in any language — whitespace in string literals is meaningful. Heck, even different spacing inside comments can change the meaning of an ASCII diagram.

    But pure formatting changes are just that. Inconsequential except for the viewer's consumption.
    Now, I'm not a diff tool connoisseur, so I can't exactly say without some looking around whether there are tools smart enough to tell meaningful whitespace changes from irrelevant ones. If there are, they definitely don't look at text as just text; they're language-aware and therefore language-dependent.


  • Discourse touched me in a no-no place

    @Zecc said:

    Now, I'm not a diff tool connoisseur, so I can't exactly say without some looking around whether there are tools smart enough to tell meaningful whitespace changes from irrelevant ones. If there are, they definitely don't look at text as just text; they're language-aware and therefore language-dependent.
    It gets complicated. For example, changing the unicode normalization form of a comment usually doesn't matter (but changes the bytes!) and it's not always important in strings either, but it can matter a lot with code. Then there's comparing XML, where you often actually need a schema-aware structure comparison.

    That said, the good thing about a language having a software-enforceable standard style is that you can get everyone to use the same style. It doesn't matter if the style isn't precisely what you'd pick; getting everyone to use the same style is the best part.



  • @Zecc said:

    even different spacing inside comments can change the meaning of an ASCII diagram

    ASCII diagrams are so 1970s. We should have a programming language that lets you embed SVG images in the comments. They're already text so it wouldn't be very hard.



  • Or maybe we should get tools that can display embedded SVG images!  =P


  • Considered Harmful

    @Zecc said:

    Or maybe we should get tools that can display embedded SVG images!  =P

    I have been sent back in time to terminate you before your ideas can spread.



  • @Zecc said:

    Or maybe we should get tools that can display embedded SVG images!  =P

    Well, yes, that was implicit in my idea. Why would you want embedded SVG images if you can't see them?


  • Discourse touched me in a no-no place

    @anonymous234 said:

    @Zecc said:
    even different spacing inside comments can change the meaning of an ASCII diagram

    ASCII diagrams are so 1970s. We should have a programming language that lets you embed SVG images in the comments. They're already text so it wouldn't be very hard.
    // See data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZlcnNpb249IjEuMSI+PHRleHQgeD0iMCIgeT0iMTUiIGZpbGw9InJlZCIgdHJhbnNmb3JtPSJyb3RhdGUoMzAgMjAgNDApIj5UaGlzIGlzIHNvIGNvb2whPC90ZXh0Pjwvc3ZnPg==

    Or we could just program in Excel.



  • @dkf said:

    @anonymous234 said:
    @Zecc said:
    even different spacing inside comments can change the meaning of an ASCII diagram

    ASCII diagrams are so 1970s. We should have a programming language that lets you embed SVG images in the comments. They're already text so it wouldn't be very hard.
    // See data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZlcnNpb249IjEuMSI+PHRleHQgeD0iMCIgeT0iMTUiIGZpbGw9InJlZCIgdHJhbnNmb3JtPSJyb3RhdGUoMzAgMjAgNDApIj5UaGlzIGlzIHNvIGNvb2whPC90ZXh0Pjwvc3ZnPg==

    Or we could just program in Excel.

    Why not just

    // See data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20version%3D%221.1%22%3E%3Ctext%20x%3D%220%22%20y%3D%2215%22%20fill%3D%22red%22%20transform%3D%22rotate(30%2020%2040)%22%3EThis%20is%20so%20cool!%3C%2Ftext%3E%3C%2Fsvg%3E

    ?


  • Discourse touched me in a no-no place

    Because the encoder I shoved it through did what it did. (Why would I spend effort on encoding something by hand? That would be TRWTF, as I've got a computer to do boring stuff for me…)



  • Re: comic thread



  • @anonymous234 said:

    @Zecc said:
    Or maybe we should get tools that can display embedded SVG images!  =P
    Well, yes, that was implicit in my idea. Why would you want embedded SVG images if you can't see them?
    I know, I was yanking your chain. Hence =P

    @joe.edwards said:

    I have been sent back in time to terminate you before your ideas can spread.
    Sometimes I feel like you guys might have a bad impression about me. Then I remember Ronald and Ben L. and I don't feel as bad.

    Seriously though, embedding images in comments would be cool, if a little terrible when seeing the source code through a plain text editor. This could solved by easily by keeping an external file and embedding only a reference to it; which incidently is the workaround you have today!

    Edit -- actually: http://visualstudiogallery.msdn.microsoft.com/793d16d0-235a-439a-91df-4ce7c721df12/


Log in to reply