Preach it, man, preach it! I'd go further - performance matters much less than 1% of the time in my experience. Maybe 0.1% would be more accurate. Even taking an edge case like Google, the performance sensitive stuff they do can't be more than a few percent of their total effort. Their best idea - map-reduce on a gigantic cluster - seems to me to be mostly a great way to speedup slow code with no programmer effort!
It's a damn shame though - optimization is such fun. HTML::Template::JIT was a blast to write, but it's worth noting that despite being the absolute hands-down fastest templating engine available it's virtually never been used. I couldn't even justify using it in a mass-mailer with very tight performance requirements, templating just wasn't the bottleneck (MIME::Lite was).
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.