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
easy to pin down too.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
It is about control (Score:1)
Me too... but, somebody had an itch... and this seems to fix it for them.
Who knows, it may help someone else too.
How can it be easier to put your Perl code in Mason components instead of Perl modules?This is a control issue.
You don't always want to give a web developer the ability to install modules into the "official" web server path... so, putting all of your Perl code into modules becomes non-trivial.
Code in Mason components is harder to unit test than Perl modules...I personally don't think you should be doing unit tests on Mason components.
The parts that need the kind of testing you are talking about should be put in a (Perl) module... and tested in the traditional manner.
The primary purpose of a Mason module (IMHO) should be to output HTML... and that output testing is done via integration testing instead of component testing.
The OOP model is confusing. As far as being up to task for anything complex... all I can really say is that Mason extends Perl.
A lot of people seem to think that MVC is the holy grail of web development... it may be. But, I think that the stateless nature of the HTTP protocol works against that.
Mason is another tool in the web developer's arsenal... and, like many things in an arsenal... it can be very dangerous when mis-used.
The trick is not to mis-use it.
Reply to This