I think you already got a couple of good answers but I want to chime in-

Catalyst rules. You can have any number of models you want. You can have DBI, DBIx::Class, Rose::DB, XML::Feed, 10 external webservices, etc, etc, etc all living together. Most of the examples show DBIC but there are no limits and the framework encourages (though doesn't force) good design choices and separation of the models. In my main personal application I have DBIC as the main model, a plaintext/line-record model for some simple human editable stuff, and I've gone through four different models to represent external feeds as my needs evolved. The only Cat assumption about models is that the model shouldn't need to know about the application (though it can if you really need it) and that the application has nothing to do with the model except for instantiating it (with configuration and arg passing) and using its "API."

Mason v Catalyst can be Catalyst + Mason. Mason is a fine view layer for Catalyst. Catalyst supports arbitrary views too. I've worked on apps that use both Mason and TT2.

Cat has a learning curve but it's fantastic and the only thing it locks you into is its dispatch mechanism which is extremely flexible and hasn't let me down since it got an overhaul about 2 years ago.

In reply to Re: Catalyst versus Mason by Your Mother
in thread Catalyst versus Mason by zerohero

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.