I suppose that depends on what you're doing, where you're doing it, who you're doing it for, and *how* you're doing it. Some solutions are certainly more effective in some cases than others while the same solution is completely inadequate in different cases.

For example, you can hand roll your own CGI parameter parsing routines and there are certainly times when that's appropriate--specifically: training exercises and when you know more than Lincoln Stein.

However, lesser mortals (like myself) writing production CGI applications under less than ideal circumstances would be wiser to use CGI.pm for their scripts.

My point being that there maybe more than one way to do it, but certain ways are useful for some situations and not others. If you're not experienced enough to know the difference, then trust the experience of those trying to help you do it the best way for the circumstances you've described.

Part of the beauty of Perl, CPAN, and the community at large is the fact that you can stand on the shoulders of giants, that you can trust their work and their advice.

When people tell you something's not the Right Way to Do Something, it may be wise to at least hear them out. They may have specific knowledge that you can learn through by sharing their experiences, rather than by repeating their mistakes. Imagine, if you will, trying to recover a cracked web server, explain to your senior VP's why your site's service was denied, or to call your customers and tell them they need to get new credit card numbers because some cracker made off with your database and is now holding it hostage--all because you thought you were a better CGI Q than Mr. Stein. I'm exaggerating, of course, but hopefully in a way that outlines the differences I'm speaking of.

Yes, Feel free to experiment in a controlled environment. However, with production data, on-line servers, and public applications...ignore well meant--and experienced--advice at your peril.

It's one thing to be confident in your abilities to figure things out and to appreciate the flexibility of the tools at your disposal. It's quite another to recognize your limitations and to accept the wisdom of others.

--f

In reply to Actually, there can be... by footpad
in thread There is no wrong way-and there is no right way either. by Swordkeeper

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.