There's more than one way to do things | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Template Toolkit is an an entire mini-language which can lead to bad practices and runs slower than most, if not all, of the other template kits while HTML::Template more strictly adheres to the purist idea of what a View RFC:SHOULD be. That sounds like a good thing at first but it hinders you, lacking all but the most simplistic loop controls and unsweetened include directives; and speed in the template layer is rarely a real issue in the full stack of a live web application. If the Template Toolkit route is appealing to you, you should know that it includes its own caching and dozens of other really nice affordances which will make your development easier, more fun and, if you can restrain yourself from going PHP on your templates, plenty manageable. :P — see also Template::Alloy for Template (TT2) compatible syntax with some of TT3 too. If you do want to go PHP on your templates, see Mason. But I keed! In reply to Re: HTML::Template Vs Template Toolkit
by Your Mother
|
|