Raymond - come out from under there! Despite Dave's particular strong preference, NOT everyone is using or should be using Catalyst.
First of all, there are other frameworks, such as CGI::Application/ Titanium and Jifty. You should at the very least compare Catalyst with these. Second of all, you don't have to use a framework to avoid "putting everything in Mason". There's a huge middle ground in there. The most important things are (1) to get complex code out of components into modules, and (2) to avail yourself of CPAN's many tools for other web functions (models, logging, etc.). For example, at Hearst where I'm consulting part-time, we serve a large number of dynamic sites through Mason and HTML::Template, without Catalyst or similar framework. We have a ton of code in libraries, we use Rose::DB and Moose for our models, Log4perl for logging, CHI for caching, Test::Class for testing, etc., and tie it together with a small "framework" that hardly deserves that moniker. Personally when I've tried to use Catalyst, the MVC stuff has gotten in my way more than it has helped me. I actually prefer dispatching from inside the view as Mason does (not that this couldn't some major modernization). I'm not saying this to start a war - this is all very specific to both developer preferences and the kind of site being built. But YMMV. Give it a try and decide for yourself! Jon On Jun 30, 2009, at 8:02 PM, Dave Rolsky wrote: > On Wed, 1 Jul 2009, Raymond Wan wrote: > >> <Hides under table> Unfortunately, not me... Any suggestions (or >> tutorials :-) ) on how to do this? Before I looked into Mason, I >> tried >> to get into Catalyst and (for some strange reason), I found it hard >> to >> get into. If everyone but me is doing it...maybe it's time to look >> at >> it again... :-) > > Catalyst is definitely harder to start with than Mason, as it has more > concepts to grok. > > Unfortunately, I think the most apt comparison here is PHP! Mason, > like > PHP, makes it easy to start, but _just_ using Mason also leads to > the sort > of "all logic in templates as a huge mess" type of programming that > PHP > leads to. > > It takes more effort to start with Catalyst, but once you do, you > have a > lot more options available, in terms of features, environments to > run in, > tools, and perhaps most importantly, writing maintainable code. > > That doesn't answer your question of where to start, though. I've > heard > mixed reviews of the one Catalyst book already out, but another is > coming > in a few weeks that I hope will be better. > > I also think that that Catalyst Manual has improved since I first > looked > (when it wasn't so great), so it's worth checking that out right now - > http://search.cpan.org/dist/Catalyst-Manual/ > > > -dave > > /*============================================================ > http://VegGuide.org http://blog.urth.org > Your guide to all that's veg House Absolute(ly Pointless) > ============================================================*/ > > ------------------------------------------------------------------------------ > _______________________________________________ > Mason-users mailing list > Mason-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mason-users ------------------------------------------------------------------------------ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
