I assume you mean that "Perl sux0rs, Java Ru1z" post. I didn't bother responding because it ammounts only to troll-feeding. There is only one question that needed to be asked of that post: is the original poster willing to show the actual code they ran in the benchmarks? This was asked by several people, but no code was forthcoming.

IMHO, not showing the code in a benchmark is the scientific equivilent of not revealing your sources. Such people are practically cursed for life for not doing such in a scientific endeavor. While that might be going too far, there is a good argument for ignoring people who aren't willing to give enough data so that others can duplicate their results.

Further, that post commited a number of logical fallacies, such as unrepresentative samples and generalizations.

So the PM community reaction was probably more than should have been done. Any response can do nothing more than feeding a troll. If the orginal poster had shown the Java and Perl implementations of the code, then we might have something to work with. Until I see the code, I see no point in giving him any respect.

----
Reinvent a rounder wheel.

Note: All code is untested, unless otherwise stated

In reply to Re: Teach him a lesson with facts by hardburn
in thread Teach him a lesson with facts by Anonymous Monk

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.