I'm all for it but let me regale you with a tale of my false economy.

I did a standalone CGI, DB driven site for myself with really some of the tightest, nicest code I've ever written. It was entirely similar to a straightforward CGI::Application or Catalyst app, using URI dispatching and method checking and such. Because it was somewhere around the 1,000th CGI I'd written, it was easy, it was clean, and it took only 3 days to write because I could lean on experience + CPAN for sessions and DB stuff.

Then I realized I wanted RSS/Atom on it. Well, there's another half day coding. Then comments. Another day or two gone and the code is now not looking so clean. I realized I'd like admin editing to work differently and have queues for drafts and published pages and be searchable and have topics/tags and Ajax and email updates and better error reporting and self-validate XHTML and... Holy crap, that is gonna be a drag... Redid it in Catalyst.

Extra tasks like those when done in Catalyst can often be as short as 10 new lines of code. Easier to read. Easier to test. Easier to maintain. Fewer chances you left some exploit accidentally. Plus more jobs for Cat devs. :)

In reply to Re^3: tt2 with perl cgi and a csv file by Your Mother
in thread tt2 with perl cgi and a csv file by Gokee2

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.