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
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Really? (Score:2)
Really? You honestly think that a webapp framework should also ship with its own object system, its own cookie parser, its own HTTP server, its own HTTP header system, and to top it off, its own new templating system!
I look at Mojo and can only think that it represents the height of foolish arrogance, and I for one am repelled by it.
Catalyst is far from perfect, but at least the Catalyst developers can concentrate on building a web framework
Re:Really? (Score:2)
Most of the "reinventing" is very thoughtfully done - and in surprisingly little code.
The template thing is indeed a little silly; but it's a very simple template module and Mojolicious has extensive support for plugging in other "renderers" (a bunch already exist on CPAN).
It's all trade-offs (of course).
With Catalyst there's a good deal of "having to learn the underlying bits" to really understand what's going on. In Mojo there's less code and it's more internally consistent.
(That being said, I do think it'd be nicer if Mojo used Moose instead of its own very basic base class).
-- ask bjoern hansen [askbjoernhansen.com], !try; do();
Reply to This
Parent