Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I have a twelve year old cross platform CGI application that I produce for 20-30 new clients every year. It uses a good amount of CPAN from a big rewrite in 2002-2003, DBI, CGI, Text::Template, etc. and a bunch of my code that does what it does. My parts of it are around 7,000 lines of code. In the next few months, I am going to internationalize the application and do my standard round of improvements and tweaks that I do every year.

That being said, is it time to look at moving to a standard framework, such as CGI::Application, Catalyst or one of the other pieces of work? If I were starting from scratch, I would certainly be looking at one of these, but I'm not starting from scratch. None of the frameworks seem to support Text::Template and I have about 300 templates done in a Text::Template format. Would adding a plugin/hook to this be terribly complicated or defeating the whole purpose of a standardized framework? I am trying to decide if the reason to move is just being a cool kid that uses a spiffy framework, or could this actually make my life easier if I continue to produce this app for another 12 years.

I still write about 30-40% of the code, but use contractors to do the rest and they have to "learn" how the whole thing goes together each time I bring a new one into the loop. Even with moving to a framework I am not sure that this won't still be the case.

Can anyone tell me about their experience porting a big CGI app to a framework? was it worth it? is there anything in this ramble that makes it obvious I should go one way or the other?

g_White

In reply to When is it worth it to move to a Framework? by gwhite

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, 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
  • 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others meditating upon the Monastery: (8)
    As of 2020-01-27 21:06 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      Notices?