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
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
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: (Score:1)
BTW. I use both and will keep using both, but I strongly prefer Mojolicious dispatcher and routes system.
But, yes, I would much prefer have it all based on Moose.
As for the other complaints, you hit and miss on them. The Mojo HTTP framework is MUCH better than any other on CPAN, from a spec-compliance point of view. Maybe thats not something that yo care about, thats ok, but it is a fact.
life is short
Re:Really? (Score:2)
And was it really impossible to work with existing authors to improve their modules? No, of course not, and it's obvious SRI had no interest in doing so.
Reply to This
Parent
Re: (Score:2)
I won't comment one way or another on what Sebastian's done because I honestly don't know his motivations, but I have a touch of sympathy for his position here. I can't tell you how many times I've discovered two things:
Re: (Score:2)
My issue is more with you promoting this as a good Perl example.
SRI can do whatever he wants, and should feel free to experiment and have fun.
But his marketing, while good from a marketing perspective, is a turn-off to me because it ignores all the existing solutions.