In short, since I just had this discussion yesterday:
- TT is language-agnostic, and works well even in languages where whitespace matters.
- TT provides heavy customization callbacks at each level of processing
- TT has an embedded language that hides the difference between hashes and
method calls so dumb hashes can be turned into smart objects later
- TT plays well outside mod_perl as a static transformation tool (or even in CGI)
- Mason has better "out of the box" caching, but TT has all the right hooks to write your own easily, probably better for real applications anyway
- TT permits Embedded Perl to be turned off or on for a given input source, useful
in an enviroment where full Perl interface would be dangerous or misleading
- embedded TT triggers can be changed to suit the parsed language, and for HTML
be selected so as to get into and out of WYSIWYG HTML wranglers without mangling
- One customer site I know doing $30M a year is using it and recommended it
highly over the other embedded Perl/HTML solutions after doing their own study
-- Randal L. Schwartz, Perl hacker
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link or
or How to display code and escape characters
are good places to start.
|
