"...the technology that gets the job done is just fine... "

That statement is of minimal use due to its overly vague and simplistic nature. The technology that "gets the job done" isn't fine if your competitors get it done in half the time, or it's easier to add features, or it's supported on more platforms, and so on (shall I add the extra 200 pages needed to summarize the major points?).

Some of us need the absolute best and place a great amount of effort into analyzing the "technology" that "gets the job done." These things can all be objectively analyzed, it just takes a very large amount of effort, time, and expertise. The scope of what languages are considered isn't anywhere near complete either, but can be filtered fairly efficiently. Due to the rapid evolution of most programming languages results don't stay current for very long either.

This is why you won't see many good comparisons posted online - they take a lot of effort, a wide area of expertise, become out of date quickly, and there's very, very little positive feedback for these things (read: you'll piss a lot of people off). So why would people bother publicizing such things?

In reply to Re: Is Perl the best programming language - a better way for discussion by Anonymous Monk
in thread Is Perl the best programming language - a better way for discussion by pg

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.