OK I understand the need/wish to do things for yourself. I've played the "dat not borned here" game myself more than once.

What confuses me is why you get so upset that people point out the modules. Just let that slide. You can't get all huffy about not having access to CPAN on this website, because, HELLO, it's a WEBSITE. And you are going to have a hard time convincing me you got perl installed on a laptop that has no floppy drive, cdrom, modem or network card.

Worse, you are going to have a real hard time convincing me that you write entire apps from scratch on your laptop in some remote mountain villa where you have no internet access.

I don't think modules off CPAN are always the answer they are often the starting point. If it is too slow, fix or replace it. If it doesn't have the capabilities, add to it, fix it or replace it.

The guy who invented the wheel deserves a lot of credit, the guys who worked to make it better deserve credit, the guy who reinvents it poorer, less featured, and more specific can't reasonably complain when people go "ho hum, you buy those at Walmart, why carve them yourself, sloppily?"

And don't get me wrong here, your code was fine and dandy and looked it through for new ideas and to see how things worked. It's just that merlyn was more than correct in pointing out that a complete, generalized version of the same trick existed in a place where we all look for code.

Code reuse is one of the Holy Grails of computing and Perl's CPAN is the singular shining example I know of that shows the promise of that quest. I can't imagine bothering to rewrite CGI when it already exists. And I doubt greatly that performance is that much of an issue that it needs a faster core. If I were to do anything, I'd condsider ripping CGI into sub modules as Mr. Stein keeps threatening to do. You'd do us all a great service by taking CGI and fixing it, you'd do us little good and yourself only moderate good by stubbornly "fixing" it yourself, blind to the YEARS of experience that have gone into making it work well for the whol community.

#erk

Whups, that turned into a rant. Sorry.

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

In reply to RE: On Perl CPAN modules by extremely
in thread On Perl CPAN modules by strredwolf

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.