I think you're generally right: RT4TJ arguments are often baseless, as the "right tool" tends to be what you have available in terms of extant code, dev tech, and people.

However, just because the argument is often misused by people who don't understand it doesn't mean it is without basis. For example, Perl is not the Right Tool when performance is King (say, 3-D model rendering and shading). Neither is Java, for that matter. You'd probably use C or ASM for something like that.

I think the fallacy comes when people start to think that for any given application there is One True Language that is the Right Tool for that job. The Right Tool argument really has more to do with narrowing the field, not the ultimate choice.

Except in those cases, the choice is less about the nature of the problem/solution, and much more about the specific constraints of the specific situation outside the problem (i.e. what resources do you have, and what work can you borrow to make your life easier).

<-radiant.matrix->
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law

In reply to Re: "The right tool for the job." by radiantmatrix
in thread "The right tool for the job." by perrin

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.