NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Catalyst is being Mooseified (Score:1)
And as I said in the title Catalyst is getting Mooseified, which from I what I see from Moose could really simplify Catalyst and make it more appealing
Re: (Score:2)
And as I said in the title Catalyst is getting Mooseified, which from I what I see from Moose could really simplify Catalyst and make it more appealing
Wow, I didn't know that ... that actually makes it less appealing to me. From what I heard & saw at YAPC::NA '08, Moose has a lot of baggage (installing Moose brings half of CPAN with it, plus the performance demands apps use mod_perl) that in my opinion, costs more than its worth.
Re: (Score:1)
Catalyst is actually already much more "unappealing" by your metrics.
Though as someone who is heavily involved in the development of both I think that's a good thing.
As for startup times, mod_perl/fastcgi/any persistent env is reccomended for Catalyst anyway, starting any app larger than a twitter clone will usually take at least a few seconds.
Before you criticise things publicly please check the facts. Heavy deps or long startup times are a legitimate concern, but the Moose chang
Code and presentation (Score:1)
I've always looked at Perl/TT like this:
Template Toolkit: Printing by default and access control flow via '[% %]'
Perl: Control flow by default and print out via 'print'
I agree, there's no sense in being a code/presentation Nazi. When the problem is emitting large chunks of output with very little control flow, then TT makes the best sense.
Bonus for factoring out presentation to a .tt.html, .tt.css, or .tt.eml file? Syntax highlighting with your editor.