That was a very good article. I have a few questions
1. You said you were biased. Which one is your favorite?
2. 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?
3. 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?
4. 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?
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.