Now it seems we are in agreement. A couple of clarifications...

The problem is only partially defining "the job." The other part is defining "done."

If you are having a hard time defining "done" that's probably because the job in question is a proverbial "job that's never done" or it was poorly defined in the first place.

The statement seems to imply that two languages can be equal for a task - they cannot.

I didn't mean to imply that. But the choice should not be made through "objective analysis" of the languages alone. The decision should be made within the context of the "job" that must be "done".

To bring this full circle and back to the original questions posed by pg, it comes down to this: if someone tells you that you picked the wrong language without being intimately familiar with the "job" you picked it for, he is talking out his ass even if he can argue the technical advantages and defend the disadvantages of his language of choice better than you can yours.

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: Re: Re: Re: Is Perl the best programming language - a better way for discussion by sauoq
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.