In short I think CGI.pm is slow bloated and unintuitive. The bloat comes from trying to support two hundred different options from generating html to parsing uris to header types and stuff ot that nature. It's slow, well, it just is! Look for benchmarks vs cgi::lite/simple. As for unintuitive, this is purely subjective of course, but I vastly prefer the cgi::lite approach where I have one method, parse_form_data, which takes a 'form data type' field and returns a nice simple hash. I can then use this hash however I want. It's simple.

In reply to Re: Re: Re: Re: Re: Really, how do I get input from the keyboard. by BUU
in thread Really, how do I get input from the keyboard. by bradcathey

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.