Re: Embperl Abandonment Issues

I'm currently at the same crossroads but my priorities are a bit different. I definitely do not want something as powerful as Embperl (or Mason or Template Toolkit) because I found it way too easy to break MVC principles. Not that it's always bad to break MVC but I still prefer my templates to be just HTML. At the moment, HTML::Template is filling the bill rather nicely (but then again it should since I prefer CGI::Application).

-derby

Comment on Re: Embperl Abandonment Issues

Replies are listed 'Best First'.
Re^2: Embperl Abandonment Issues by andreas1234567 (Vicar) on Sep 08, 2008 at 07:58 UTC
I definitely do not want something as powerful as Embperl (or Mason or Template Toolkit) because I found it way too easy to break MVC principles. I agree. I have used HTML::Mason extensively over the last 4 years, and I really like the power and flexibility it provides. But these strengths can also become weaknesses, and it can be very easy for inexperienced developers to break MVC principles without even knowing it. -- No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]	[reply]
Re^2: Embperl Abandonment Issues by blazar (Canon) on Sep 13, 2008 at 13:26 UTC
I personally believe you won't be interested at all since it is by definition even more poweful and complex, but since nobody seems to have mentioned it yet, there's also Template::Alloy, (I've never used it, but ever since I heard of it for the first time, I liked the idea!) by a fellow monk of ours, whose PM handle unfortunately I can't remember ATM: it gives convenient access to several templating systems mini-languages, so one can just choose the one she likes best for any particular task, being allowed to mix them freely. (Sorry for replying so late!) `--` If you can't understand the incipit, then please check the IPB Campaign.	[reply] [d/l]