I understand "target CGI" to mean "output the HTML myself", and "run via the CGI protocol" (instead of some kind of server, like mod_perl).

So I don't see why one shouldn't or couldn't think about maintainability, scalability, reliability and template delimiters when targetting CGI.

Also, while I fully support that experience is something you have to do yourself, there certainly are ideas that are so bad that they don't need to be explored. But you don't give any actual arguments as to why CGI shouldn't be explored, and you don't give any arguments as to why the choice of delimiter doesn't matter.

In reply to Re^2: Issues and Advantages module Text::Template (opinions) by Corion
in thread Issues and Advantages module Text::Template by itztheMonk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.