in reply to A "newbies" thoughts on cgi.pm...

So let's see, basically you don't want to use CGI.pm because you did not write it, hence it doesn't behave exactly as you want, plus you don't use all of it.

Now why don't you apply that same line of thought to Perl, after all you did not write it, and maybe you don't like the $#array construct, after all no one seems to like it that much. Plus I would be ready to bet that you don't use all of it, like blessing colsures into objects, or anything that Dominus or TheDamian do routinely in their abject perversions of the language. Plus the code is huge, and hard to read, so really, you should not be using it I think.

And what about the web server, that's the piece of code that calls your CGI script, remember, if it's Apache, man what a huge software, hard to read, do you use all of its features? I hope not! And if it is IIS you can't even read the code..

No really, logically you should code the web server and your CGI script, all in assembly language.

No? Doesn't make sense? Then maybe you should realize that using trusted code is not so bad after all. I know if I was working with I'd feel _very_ uncomfortable if I heard you explain why you don't want to use the best tools available.

chromatic has a nice piece on it in his journal on Use Perl.</p.