(MeowChow) Re: Choosing a Templating System

It would be nice if the full text of this article was in the tutorials section. With yours and our editors' permission, I would that it were so.

   MeowChow                                   
               s aamecha.s a..a\u$&owag.print

Comment on (MeowChow) Re: Choosing a Templating System

Replies are listed 'Best First'.
Re: (MeowChow) Re: Choosing a Templating System by perrin (Chancellor) on Aug 16, 2001 at 00:57 UTC
The trouble is, then I'd have mutiple places to update it, and I do plan to update it. It's a lot easier just to link to it from here.	[reply]
Re^3: Choosing a Templating System by mds (Novice) on Apr 19, 2013 at 02:26 UTC
That was a very good article. I have a few questions You said you were biased. Which one is your favorite? If the Perl Gods decreed that there were no more templating systems to be created and no new functionality to be added to existing ones save for security and bug fixes and that you had to choose one templating system to use for the rest of your life, which one would you choose, at this point in time? Maintainability may be difficult to define, but part of it is being able to quickly read and learn another programmers code. Which one would you choose for maintainability assuming you will be handing the application off to someone who is as good or better then you at coding? Which one would you choose for ease of learning but at the same time gives the biggest return for time spent on using it? I don't think these are simple questions and they could be more well defined and I'm sure the answers could be long and detailed. I'm just looking for a simple, direct and unfiltered bias. I only have time to learn one and I don't have time to maintain it. (The assumption here is standardized, "well writen" code) So which one would you choose?	[reply]


Welcome to the Monastery
	PerlMonks