Usually, people say they are writing a new one because it's faster or easier or does something that the old one doesn't. Usually, they are also flat-out wrong about these assertions, and would have known it if they had spent a little more time looking at the existing solutions.
It doesn't harm me if someone who I don't work with writes their own templating system. But what if they put it on CPAN and add to the pile of half-baked unmaintained solutions that swamp anyone searching for a templating system there? What if I have to work on some of their code someday, and it uses this monstrosity?
And the more subtle issue is, how much better might TT be if people tried to improve it instead of writing their own half-assed version that gets tossed out in a year?
There are real reasons why re-inventing the wheel is usually wrong. Ask anyone who had to support someone else's bespoke templating system at their company. It's not just a knee-jerk reaction.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.