I think the costs are more significant than that. A lot of talented people spent a lot of time thinking hard, finding solutions, crafting answers, testing code, and posting their responses, when there wasn't actually any need for them to do so. The plagiarized posts often seem like good topics, and on some level it's sort of nice to have a local archive of answers. But since those questions were already answered at least once before elsewhere on the web, duplicating that effort is of limited value. (Especially since searching PerlMonks is more difficult than it ought to be.)
That's a lot of hours frittered away, and for what? A couple fools got inflated PerlMonks XP? It's a real boggle that these two would so cavalierly waste our precious time and expertise for something so trivial.
-
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.
|