The points in your question that I'd agree with are that more books on specific topics are good and that Perl books are often very generalized. Yes, this can be a handicap for the rawest newbies, but anybody with any exposure to programming in the Cold Cruel WorldTM quickly wants to do more than say 'Hello, World' in FONT SIZE='7'. It is very true that PHP has benefitted from the fact that its TIOOWTDI constraints make books easy to write clearly. It has a very limited problem domain, and thus there aren't many options to write about.

I don't think we need to focus on one templating system. I don't see books on TT being in conflict with books on Catalyst or Embperl. Better to have books on all three!

A good example of why having multiple options is a positive virtue: OpenBSD has probably the smallest user community of all BSD and linux variants, but every single one of the others now includes OpenSSH, and the same thing is happening with the pf security construct. Cross-pollination between open source projects means that good features get propagated in many directions.

Don Wilde
"There's more than one level to any answer."

In reply to Re: Perl mindshare in web development by samizdat
in thread Perl mindshare in web development by gunzip

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.