in reply to Re: Re: Get input data from STDIN *and* query string
in thread Get input data from STDIN *and* query string

All right, all right, fine...If I'm gonna get flamed everytime I contribute something, I just won't contribute anything...Though I don't see why you'd want to ram advice down my throat, it's not like you HAVE to use my code.  I gotta say, I'd expected a little less childish behavior here.

______________________________________________
If the world didn't suck, we'd all fly off.
       -A friend of mine

  • Comment on Re: Re: Re: Get input data from STDIN *and* query string

Replies are listed 'Best First'.
(tye)Re: Get input data from STDIN *and* query string
by tye (Sage) on Jan 10, 2001 at 23:31 UTC

    Yes, please! I was very dismayed to see a call for downvotes and then a gloating over a node going to worst nodes of the week. Childish is a very good description of it. I hope we can avoid this in the future.

    I'm sorry, EvanK.

            - tye (but my friends call me "Tye")
[reply]
      Thanks tye, I'm glad there's someone here that isnt out to get me because I write my own code...and if someone had just calmly explained those "security risks" and actually proved me wrong instead of going wild and flaming me without giving me a reason, then I wouldnt have gotten offended.

      ______________________________________________
      If the world didn't suck, we'd all fly off.
             -A friend of mine

[reply]
        Those explanations have happened repeatedly in this venue and others. And maybe we shouldn't be so quick to presume that you've seen them, but then again, the damage that your code causes in propogating a bad meme requires swift innoculation, lest someone see your bad code and not notice the correction.

        The cargo culting of "read(STDIN, $buf, $ENV{CONTENT_LENGTH})" in all those "teach yourself CGI in 37 microseconds" has not helped. Maybe I'm particularly sensitive about that, since CGI.pm is just too frickin easy to use, and is already installed with all modern Perl distributions.

        -- Randal L. Schwartz, Perl hacker

[reply]
Re (tilly) 4: Get input data from STDIN *and* query string
by tilly (Archbishop) on Jan 11, 2001 at 00:13 UTC
    While I didn't like the appearance of the mob scene, there are excellent reasons why your code got flamed. I suggest that you take some time out to find out what is and is not available before you start contributing large amounts of code. The search box in the upper left corner is an excellent place to start. Super Search is an excellent place to continue (but it is harder on the server). If you need to then ask in chatter where stuff is on foo before submitting code about foo.

    Otherwise when you submit advice and there are problems with it, people will (sometimes loudly) inform the world of the problems in it. Not for their good. And possibly not really for yours. But so that nobody else will be tempted to make the mistakes that you are recommending.

    Incidentally you will find that people tend to be very kind on people asking questions in SoPW, fairly kind within conversation threads, somewhat more critical to people offering snippets and code samples, and very critical very fast if you offer bad advice which is bad for reasons that come up regularly.

    You did the last, which is why you got such an extremely negative reaction.

[reply]
      Yeah, i did the same thing my first day here :) just gotta learn the ways of these wise monks. The people here are really cool, just take some time to get to know them first
[reply]
Re: Re: Re: Re: Get input data from STDIN *and* query string
by ichimunki (Priest) on Jan 11, 2001 at 00:12 UTC
    Okay. I won't use your code. Unless your code adds something to the functionality of CGI.pm which you aren't telling us about, you are rewriting software that every default install of Perl has with it. It seems like a waste of time for me to install and test your code when I can accomplish the same thing with a lot more confidence in two lines of code using CGI.pm (albeit without the apparent subversion of the HTTP standard).

    I do agree that a few silent downvotes and a polite comment or succinct criticism are better than calls for downvote stampedes. On the other hand, what if you get a job working on the website for somebigcorp.com someday? I might be using your code without even knowing it, and I'd rather a few bruises to your ego now than a compromised e-commerce site down the road. Code posters should be receptive to criticism, and those who criticize should be firm, but polite, if they expect the advice to be heeded.
[reply]
      Well, the smartest course of actuion rather than getting everyone to wanna lynch me, would be to prove me wrong, explain to me why I'm wrong. I'm not at fault here. And I removed the code, so stop persecuting me. Jeez...

      ______________________________________________
      When I get a little money, I buy books. If I have any left over, I buy food and clothes. -Erasmus

[reply]
        I was suprised to find this post marked down. Well not suprised since people seem to be freer with the -- than they used to be. I run out of votes every day just bumping up the good stuff, I can't figure out WHY anyone would bother downticking this.

        --
        $you = new YOU;
        honk() if $you->love(perl)

[reply]

In Section Cool Uses for Perl