PsychoSpunk, I am not saying that a discussion of the relative
merits of two different ways of doing something isn't appropriate.
Unfortunately, that is not how the original post appears to my eyes.
Though it easily could have been written in such a fasion, instead
it appears as a defensive position for an article not published here,
against a criticism, also not published here. This kind of defensive
posturing is hardly conducive to open minded discussion and more like
a pissing match (even if only one party is actually pissing). If princepawn
merely wanted to open a discussion about the relative merits of
DBIx::Recordset vs. DBI, and evangelize the former, why bring in the
excess baggage of the article and criticism in the first place
(because, it appears, he didn't come to open a discussion about
DBIx::Recordset vs DBI, he came to defend his article -- and his
follow-up to chromatic looks like more of the same). I don't know
about you, but thus far I haven't seen anything really new here beyond
arguments for, and restatements of, the original perl.com article's content.
I am glad you find it so fascinating though.
-
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 How to display code and escape characters
are good places to start.
|