A year or two ago I ran across an interesting study on exactly this that was done several years ago. I can't find the study right now (I'd appreciate it if anyone who knows the one I'm talking about could post it), but the idea was that they took a reasonably complex but well defined problem and had it implemented by a variety of programmers in a variety of languages (C and Perl were in the list). They then compared how long the solutions took to implement, and how rapidly they ran.

As you might expect, the most rapidly implemented solutions were the ones done in the scripting languages. The fastest solutions were in C.

As you might not expect, the slowest solutions were in C. Furthermore the variation both in time to implement and runtime performance were far larger in C than in scripting languages.

What seemed to happen is that the scripting languages provided an obvious good approach to the problem, and everyone took that with decent results. In C there were many choices to make, with more difficult to see consequences for time to implement and runtime performance. (Which is exactly what you are talking about having happen.)

I'd wager that Java would have resembled C in this particular test, but without the performance.

In reply to Re: There's Only One Way To Do It by tilly
in thread There's Only One Way To Do It by jdporter

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.