Repeated rounds of your ignoring outside input and continuing on a tangent is not operating in a scholarly fashion. In addition your use of the word "discuss" presumes that I think you are bringing something particularly useful to the table.

The fact was, and remains, that the quality of the example code in your original paper was so uniformly low that it completely overwhelmed the potential respective merits of the two modules. (Those who think I am being too harsh should read my analysis first.) Therefore your original paper was utterly useless as a way of exploring those issues.

Your new point which tries to say that programmatic production of text is better (either HTML or SQL) is again not a useful analogy. In fact your opinion on this matter does not reflect awareness of the basic value of separating content and presentation. That is why (quite contrary to what you appear to think is the consensus on producing HTML) most experienced programmers believe that it is valuable to use a templating system if you are trying to manage a complex website.

Moving logic into code is not always the right thing to do. It certainly is not worth doing just to be able to say that you did it!

In reply to Re (tilly) 3: Rebuttle to chromatics by tilly
in thread Rebuttle to chromatics by princepawn

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.