Thanks for linking to my site :-)

Anyway,

Having a (couple of) good framework(s) to start with will certainly help you get a handle on the problem. In the end though, there's nothing like building something from scratch to really find out where the difficulties and trade-offs are for that particular problem.

I'm not sure what I would suggest if your goal is to learn as much as possible. Probably to try a few different frameworks, maybe learn one or two of them fairly well, and then possibly try and create some framework better suited to some new problem that doesn't get served very well with the existing ones.

Note that none of this is particularly about learning Perl. Having a good overview of (how to deal with) the problems in your domain is more useful than having in-depth knowledge of the programming language "of the moment". But using a good framework will also help you understand Perl better, and if the choice is between writing a new framework with minimal perl knowledge and using an advanced framework (and so, being exposed to probably more advanced perl code), you might just learn more (Perl) by using the existing stuff.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re: Is using Catalyst cheating? by Joost
in thread Is using Catalyst cheating? by actualize

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.