Excellent point: ++.
CGI.pm is definitely been better than what most new programmers
could write on the first try. But by the same token, it would be
easier for most people to write their own CGI handler, MIME parser,
browser isolation layer, and formatting system than to figure out
My own objection to CGI.pm is the interface itself. Interfaces are protocols,
and ideally, a library interface should be easier to learn and use than the thing it abstracts. I'd personally argue that CGI.pm's interface is both harder to learn and less flexible than the CGI per se.
It didn't start that way, but bloat is part of the natural software lifecycle. When
something gets so big and unwieldy that people would rather reimplement it than
learn the existing version, it's time to clean house. The new versions aren't waste,
they're competition, and competition is a Good Thing.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||