Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

autarch (914)

autarch
  (email not shown publicly)
http://www.vegguide.org/

Journal of autarch (914)

Wednesday May 02, 2007
10:20 AM

A brief followup to "Why I don't like TT"

[ #33178 ]

I just want to clarify something about my Why I don't like TT entry.

When reading it, don't implicitly add anything like "and therefore TT sucks", or "and therefore you should never use TT" at the end.

That was not my intent. My goal is simply to explain some issues that I have experienced with TT. I think they're important to consider when you look at templating systems, and these particular problems are also very much non-obvious. They're not an obvious limitation like not having some feature, rather they're fundamental design issues arising from the design of the language.

Similarly, my intent was not imply that because I don't like TT, someone else should use Mason. Personally, I would choose Mason whenever I'm given the choice, but that's done knowing its limitations and potential pitfalls, which would be a good topic for another entry.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • In line with mjd's old article, http://www.perl.com/pub/a/2000/12/advocacy.html [perl.com], on why he hates advocacy, where he makes similar points.

    I was just reading that, led to it by a reply to a vituperative anti-perl message on a haskell list.

    Ecumenicism is good. Now I just have to overcome my own commitment by trashing it and perl together :-)