• SilverEyes (unregistered) in reply to Anonymous
    Anonymous:
    getofmymetriclawn:
    SoaperGEM:
    No. "Frist" was never funny to begin with. It's just beating a dead horse. A very, very, very dead horse.
    Yes, but by also using the "reusing the WTF-pattern in the article with some meta-reference to the comment" meme, he is beating one dead horse with another dead horse, which could, in theory, still be funny.
    Eh, maybe. If he was beating a dead horse with a dead horse whilst riding a dead horse over a pile of dead horses, that would be funny.

    Now you're just beating a dead horse.

    CAPTCHA: appellatio , don't even ask what my first thought was

  • (cs) in reply to Ubermensche
    Ubermensche:
    no it isn't:
    lAng=frist

    this is still funny right?

    Not relaly, lAng=Fritz is funnier.

    Only though if you're in Metropolis.

    Please don't reference that dumb movie. It should be left for pseudo-intellectual yuppies to revere.

  • (cs) in reply to frits
    frits:
    You have to love how VB.Net has its own special namespace with slightly different implementations of already available string methods.
    They're there for backwards compatibility only. Most are much more tolerant of null strings and they guarantee that upgraded VB6 string handling code will function as originally intended. You don't have to use them for new work.
  • neminem (unregistered) in reply to Stacy
    Stacy:
    I dunno... I think once you have more than 3 dead horses it becomes less funny and more sad.
    Beating one dead horse is a tragedy; beating a million dead horses is a statistic?

    Second page!

  • Joe (unregistered)

    Oh come on. He could have at least put them in order so it's easy to tell if he's already covered the next possibility that needs to be added. en, eN, En, ...

  • (cs) in reply to Jaime
    Jaime:
    frits:
    You have to love how VB.Net has its own special namespace with slightly different implementations of already available string methods.
    They're there for backwards compatibility only. Most are much more tolerant of null strings and they guarantee that upgraded VB6 string handling code will function as originally intended. You don't have to use them for new work.

    Yeah, I know about that justification. Unfortunately, backward compatibility between legacy VB and VB.net is severely limited. I have actually never seen a direct port from VB 6 to VB.Net. It's much more common, in my experience, to see a rewrite of a VB 6 app in C#.

  • (cs) in reply to SilverEyes
    SilverEyes:
    Anonymous:
    getofmymetriclawn:
    SoaperGEM:
    No. "Frist" was never funny to begin with. It's just beating a dead horse. A very, very, very dead horse.
    Yes, but by also using the "reusing the WTF-pattern in the article with some meta-reference to the comment" meme, he is beating one dead horse with another dead horse, which could, in theory, still be funny.
    Eh, maybe. If he was beating a dead horse with a dead horse whilst riding a dead horse over a pile of dead horses, that would be funny.

    Now you're just beating a dead horse.

    "Look, kid, it's dead horses all the way down!"

  • wtf (unregistered) in reply to frits
    frits:

    Please don't reference that dumb movie. It should be left for pseudo-intellectual yuppies to revere.

    Please keep your nouns and verbs straight. This is a family web site.

  • (cs) in reply to wtf
    wtf:
    frits:

    Please don't reference that dumb movie. It should be left for pseudo-intellectual yuppies to revere.

    Please keep your nouns and verbs straight. This is a family web site.

    I'm going to need some clarification. Perhaps there's some sort of snobbery I'm not picking up on?

  • Murry (unregistered)

    This would have been a good place for some XML. Somehow. Right?

  • French Boy (unregistered)

    This reminds me of one time with Irish Girl. I thought I could probably get the job done in one short expression, but she kept wanting me to go again, again, again, again, again, changing my technique a little bit each time, again, again, again, bigger letters, bigger, bigger, what about something Greek...

  • (cs) in reply to frits
    frits:
    Jaime:
    frits:
    You have to love how VB.Net has its own special namespace with slightly different implementations of already available string methods.
    They're there for backwards compatibility only. Most are much more tolerant of null strings and they guarantee that upgraded VB6 string handling code will function as originally intended. You don't have to use them for new work.

    Yeah, I know about that justification. Unfortunately, backward compatibility between legacy VB and VB.net is severely limited. I have actually never seen a direct port from VB 6 to VB.Net. It's much more common, in my experience, to see a rewrite of a VB 6 app in C#.

    I did it last year. About 50K lines of code, maybe a dozen sections needed a rewrite and at least 75% of the code wasn't touched.
  • h (unregistered)

    so easy.

    <?
    
    define ('l', array('l', 'L'));
    define ('a', array('a', 'A'));
    define ('n', array('n', 'N'));
    define ('g', array('g', 'G'));
    define ('e', array('e', 'E'));
    
    for ($ll=0;$ll<=1;%ll++) {
      for ($aa=0;$aa<=1;%aa++) {
        for ($nn=0;$nn<=1;%nn++) {
          for ($gg=0;$gg<=1;%gg++) {
            for ($ee=0;$ee<=1;%ee++) {
              for ($nn2=0;$nn2<=1;%nn2++) {
                MyPage = Replace(MyPage, "&".$l[ll].$a[$aa].$n[$nn].$g[$gg]."=".$e[$ee].$n[$nn2].", "")
    }}}}}}
    
    ?>
    

    //untested.

  • (cs) in reply to Jaime
    Jaime:
    frits:
    Jaime:
    frits:
    You have to love how VB.Net has its own special namespace with slightly different implementations of already available string methods.
    They're there for backwards compatibility only. Most are much more tolerant of null strings and they guarantee that upgraded VB6 string handling code will function as originally intended. You don't have to use them for new work.

    Yeah, I know about that justification. Unfortunately, backward compatibility between legacy VB and VB.net is severely limited. I have actually never seen a direct port from VB 6 to VB.Net. It's much more common, in my experience, to see a rewrite of a VB 6 app in C#.

    I did it last year. About 50K lines of code, maybe a dozen sections needed a rewrite and at least 75% of the code wasn't touched.

    OK, I stand corrected. There is a use for the legacy VB stuff. Out of curiousity, what was the application?

  • (cs) in reply to vovo
    vovo:
    m a t t:
    savar:
    This is an instantly fire-able offense.
    What? Beating dead animals with other dead animals?

    Why are we beating a dead horse with another dead horse? Let's start beating the guy beating the dead horse with another dead horse.

    A quite common mistake... leads to infinite recursion. You have to beat the guy beating the dead horse, with a (dead horse - 1)

  • wtf (unregistered) in reply to frits
    frits:
    I'm going to need some clarification. Perhaps there's some sort of snobbery I'm not picking up on?

    Verbing your nouns annoyings readery people.

  • Ralph (unregistered) in reply to wtf
    wtf:
    frits:
    I'm going to need some clarification. Perhaps there's some sort of snobbery I'm not picking up on?

    Verbing your nouns annoyings readery people.

    OK, you're claiming he verbed a nouner, but where? The original sentence looked fine to me.

  • GrammarWTF (unregistered) in reply to Anonymous
    Anonymous:
    getofmymetriclawn:
    SoaperGEM:
    No. "Frist" was never funny to begin with. It's just beating a dead horse. A very, very, very dead horse.
    Yes, but by also using the "reusing the WTF-pattern in the article with some meta-reference to the comment" meme, he is beating one dead horse with another dead horse, which could, in theory, still be funny.
    Eh, maybe. If he was beating a dead horse with a dead horse whilst riding a dead horse over a pile of dead horses, that would be funny.

    Yo dawg, I heard you like dead horses, so I beat a dead horse with a dead horse while commenting about a dead horse!

  • RFC Reader` (unregistered)

    TRWTF is that people seriously think that "applying some substring finesse" or regexes are a solution to this problem, as opposed to using URI parsing functionality built into the framework. URI parsing is hard if you care at all about getting it right, read the URI RFC - it's a nightmare

  • anon (unregistered) in reply to Ralph
    Ralph:
    wtf:
    frits:
    I'm going to need some clarification. Perhaps there's some sort of snobbery I'm not picking up on?

    Verbing your nouns annoyings readery people.

    OK, you're claiming he verbed a nouner, but where? The original sentence looked fine to me.

    nowhere. not one verb in the original sentence was originally a noun. no idea what these morons are talking about, but I really hope it's not "revere".

  • (cs) in reply to anon
    anon:
    Ralph:
    wtf:
    frits:
    I'm going to need some clarification. Perhaps there's some sort of snobbery I'm not picking up on?

    Verbing your nouns annoyings readery people.

    OK, you're claiming he verbed a nouner, but where? The original sentence looked fine to me.

    nowhere. not one verb in the original sentence was originally a noun. no idea what these morons are talking about, but I really hope it's not "revere".

    I think he's refering to "reference". Which was a noun but is now definitely a verb in American speech as well as in computer science circles. I am certainly not going de-refer-to my pointers.

  • (cs) in reply to frits
    frits:
    Jaime:
    frits:
    Jaime:
    frits:
    You have to love how VB.Net has its own special namespace with slightly different implementations of already available string methods.
    They're there for backwards compatibility only. Most are much more tolerant of null strings and they guarantee that upgraded VB6 string handling code will function as originally intended. You don't have to use them for new work.

    Yeah, I know about that justification. Unfortunately, backward compatibility between legacy VB and VB.net is severely limited. I have actually never seen a direct port from VB 6 to VB.Net. It's much more common, in my experience, to see a rewrite of a VB 6 app in C#.

    I did it last year. About 50K lines of code, maybe a dozen sections needed a rewrite and at least 75% of the code wasn't touched.

    OK, I stand corrected. There is a use for the legacy VB stuff. Out of curiousity, what was the application?

    An internal telesales application at work. Mostly boring order entry stuff, but a few interesting things like telephony integration. The telephony part was almost worthy of this site for a while. We originally added it after we knew we were moving to .Net, but before the actual conversion. So, we wrote it as a .Net class library and exposed it to the app via COM. The pinheads that migrated this part put an interop wrapper around the COM wrapper.
  • wtf (unregistered) in reply to frits

    Reference is what is achieved when you refer. It's a common mistake, but so are drunk driving and voting Republican, that doesn't make either of them right.

    "Dereference" is a domain-specific coinage with no counterpart in ordinary English, and it doesn't seem to like back-formation. I have a pointer and I'm going to use it to reference a variable? No, I'm going to point to the variable.

  • anon (unregistered) in reply to wtf
    wtf:
    Reference is what is achieved when you refer. It's a common mistake, but so are drunk driving and voting Republican, that doesn't make either of them right.

    "Dereference" is a domain-specific coinage with no counterpart in ordinary English, and it doesn't seem to like back-formation. I have a pointer and I'm going to use it to reference a variable? No, I'm going to point to the variable.

    well, people have only been using reference as a verb for about 150 years, so I can see how one would get confused by these newfangled usages. I mean, my car gets 5 rods to the hogs head and that's the way I likes it.

  • (cs) in reply to wtf
    wtf:
    Reference is what is achieved when you refer. It's a common mistake, but so are drunk driving and voting Republican, that doesn't make either of them right.

    "Dereference" is a domain-specific coinage with no counterpart in ordinary English, and it doesn't seem to like back-formation. I have a pointer and I'm going to use it to reference a variable? No, I'm going to point to the variable.

    The irony of it all is that I was originally poking fun at pseudo-intellectuals, which obviously butt-hurted you.

  • (cs) in reply to RFC Reader`

    Awesome, this guy didn't know about the HttpUtility.ParseQueryString method that's been around for five years.

    http://msdn.microsoft.com/en-us/library/ms150046.aspx

  • Stephen Cleary (unregistered) in reply to frits
    frits:
    wtf:
    Reference is what is achieved when you refer. It's a common mistake, but so are drunk driving and voting Republican, that doesn't make either of them right.

    "Dereference" is a domain-specific coinage with no counterpart in ordinary English, and it doesn't seem to like back-formation. I have a pointer and I'm going to use it to reference a variable? No, I'm going to point to the variable.

    The irony of it all is that I was originally poking fun at pseudo-intellectuals, which obviously butt-hurted you.

    I love how elitist liberals have become!

    http://www.youtube.com/watch?v=ZPQtjJ55SMA

  • North Shore Beach Bum (unregistered)

    According to dictionary.com, "The verb first is attested 1884."

    Methinks someone fell victim to Muphry's Law.

  • Hugh Brown (unregistered) in reply to North Shore Beach Bum

    Muphry's Law: if it's possible to commit a typo, you will. Muphry's Law, Daily WFT corollary: if it's possible for a website to contain a typo, it will occur at www.dailywtf.com frist.

  • MindChild (unregistered) in reply to Ralph
    Ralph:
    That looks like some perfectly normal VB to me. Yes it would be atrocious in other languages, but again, perfectly fine VB!

    Strawman. The language has nothing to do with it, other than VB makes non programmers think they can program.

    Dim MyPage As String = Replace(Replace(Request.Url.ToString, "lang=gr", "", vbCompareText), "lang=en", "", vbCompareText)

    THAT is perfectly acceptable VB. The original code is what happens when you throw a baby into the deep end of the pool

  • wtf (unregistered) in reply to frits
    frits:
    The irony of it all is that I was originally poking fun at pseudo-intellectuals, which obviously butt-hurted you.

    No, it was the language fail that gave me pain. Couldn't give a rip about Metropolis, except for historical interest.

  • Skilldrick (unregistered) in reply to Stacy
    Stacy:
    Anonymous:
    getofmymetriclawn:
    SoaperGEM:
    No. "Frist" was never funny to begin with. It's just beating a dead horse. A very, very, very dead horse.
    Yes, but by also using the "reusing the WTF-pattern in the article with some meta-reference to the comment" meme, he is beating one dead horse with another dead horse, which could, in theory, still be funny.
    Eh, maybe. If he was beating a dead horse with a dead horse whilst riding a dead horse over a pile of dead horses, that would be funny.

    I dunno... I think once you have more than 3 dead horses it becomes less funny and more sad.

    I literally LOL'd.

  • (cs) in reply to wtf
    wtf:
    frits:
    The irony of it all is that I was originally poking fun at pseudo-intellectuals, which obviously butt-hurted you.

    No, it was the language fail that gave me pain. Couldn't give a rip about Metropolis, except for historical interest.

    Pointing out perceived errors in grammar on the internet is the height of pseudo-intellectual snobbery. Therein lies the irony. Keep up.

    Bonus points for being wrong.

  • Andy (unregistered) in reply to frits
    frits:
    wtf:
    frits:
    The irony of it all is that I was originally poking fun at pseudo-intellectuals, which obviously butt-hurted you.

    No, it was the language fail that gave me pain. Couldn't give a rip about Metropolis, except for historical interest.

    Pointing out perceived errors in grammar on the internet is the height of pseudo-intellectual snobbery. Therein lies the irony. Keep up.

    Bonus points for being wrong.

    Dead wrong, even, dare I say.

  • Rolly Paulie (unregistered) in reply to MindChild
    MindChild:
    The language has nothing to do with it, other than VB makes non programmers think they can program.
    And that has everything to do with it!!! That's why VB is TRRFWTF (The Real Recursive Forever WTF).
  • Cliff notes anyone (unregistered) in reply to SR
    SR:
    MyComment = Replace(MyComment, "FRIST", "SECOND")

    frist

    fixed

  • (cs)

    LANG=XX

    Just 2^4 * 1 /* the =-sign / * 52 / upper/lower case */ ^2

    which gives us 43264 combinations. Some less because we do not need all 52^2 letter combinations.

  • Rodger C. (unregistered)

    YouTube's <embed>ded video URLs never have a ? in them. They work whether the first query-string parameter begins with a "?" or with a "&".

    CAPTCHA: distineo (sounds like a Harry Potter curse, amirite?)

  • Duke of New York (unregistered)

    I can't wait to see his code for adding two numbers

  • wtf (unregistered) in reply to frits
    frits:

    Pointing out perceived errors in grammar on the internet is the height of pseudo-intellectual snobbery. Therein lies the irony. Keep up.

    Bonus points for being wrong.

    Wrong? Try a little elementary morphology. "Reference" is a derived noun, derived from a perfectly good verb, "refer". Are you going to tell me that "difference" is a verb? I prefer to speak English, my friend. Or should that be "I preference to speak English"?

  • Gary Olson (unregistered) in reply to frits
    frits:
    Anonymous:
    Why not just convert the query string to all lower (or upper) case and then just remove the "lang=el" part of it?

    How would you put it back to its previous capitalization? ;)

    Convert back to the original Klingon. Klingon is predominately spoken in capitals.

  • Stalin (unregistered) in reply to Stacy
    Stacy:
    I dunno... I think once you have more than 3 dead horses it becomes less funny and more sad.
    But once you have a million dead horses, it becomes a statistic.
  • Some Dude (unregistered) in reply to MindChild
    MindChild:
    Dim MyPage As String = Replace(Replace(Request.Url.ToString, "lang=gr", "", vbCompareText), "lang=en", "", vbCompareText)

    THAT is perfectly acceptable VB.

    It fails to actually achieve the correct result, and doesn't handle case sensitivity correctly. And that's assuming that only handling two specific languages was the actual requirement.

    When you say that it is perfectly acceptable VB, I believe you.

  • the beholder (unregistered) in reply to Ralph
    Ralph:
    wtf:
    frits:
    I'm going to need some clarification. Perhaps there's some sort of snobbery I'm not picking up on?

    Verbing your nouns annoyings readery people.

    OK, you're claiming he verbed a nouner, but where? The original sentence looked fine to me.
    Oh no, revere is a noun. Haven't you ever heard about The Midnight Ride of Paul Revere?

  • Bingo (unregistered) in reply to Anonymous

    I'm on a horse.

  • Gary (unregistered) in reply to Knux2
    Knux2:
    I would love to see how he would handle "Replace any 6 digit numbers with their hexadecimal equivalents."

    MyPage = Replace(MyPage, "000000", "00000") MyPage = Replace(MyPage, "000001", "00001") MyPage = Replace(MyPage, "000002", "00002") MyPage = Replace(MyPage, "000003", "00003") MyPage = Replace(MyPage, "000004", "00004")

    ...

    MyPage = Replace(MyPage, "999999", "F423F")

    Oh, why make it so easy and pad the numbers with zeroes? Would be much more, uh, interesting if you made it something like this...

    MyPage = Replace(MyPage, "0", "0") ... MyPage = Replace(MyPage, "10","A") ... MyPage = Replace(MyPage, "16","10")

    and even better if it ran from 999999 backwards... I'm almost tempted to write this just to see how it would come out...

  • James (unregistered)

    Welcome to the world of MS case-insensetive coding that should not have been a problem with LaNg in the first place. I wonder if the handled the case where the parameter isn't actually the first because the it would have had a & and not a ? - but they can probably fix that too ;)

  • Mumba-Jumba (unregistered)

    Very clean code that works, he-he.

  • anon (unregistered) in reply to Stacy
    Stacy:
    Anonymous:
    getofmymetriclawn:
    SoaperGEM:
    No. "Frist" was never funny to begin with. It's just beating a dead horse. A very, very, very dead horse.
    Yes, but by also using the "reusing the WTF-pattern in the article with some meta-reference to the comment" meme, he is beating one dead horse with another dead horse, which could, in theory, still be funny.
    Eh, maybe. If he was beating a dead horse with a dead horse whilst riding a dead horse over a pile of dead horses, that would be funny.

    I dunno... I think once you have more than 3 dead horses it becomes less funny and more sad.

    Come on guys. Dead is an absolute. We mock the WTFs that make abolutely, positively sure that "something==True". The horse is just dead. Or NOT_FOUND.

  • (cs)

    Yo dawg, I herd yo like replacing Strings. So I replaced your String with a String replacement so that you can replace your String while your String is replaced, dawg.

Leave a comment on “RePLaCeD”

Log In or post as a guest

Replying to comment #:

« Return to Article