perrin++

The "right tool" argument is generally used to support whatever your favorite tool is. The flame warrior might then mumble something about hammers and screwdrivers. The problem is that those are both very simply tools, and it's quite clear when you should use one over the other. Programming languages are very complex tools. In almost any sizeable application, it would take a huge study to know what language(s) would be best for the application. This study might take as long as just writing it in whatever language you have on hand.

Further, any given section of an application might be better suited to a language other than the one you're using. Chances are, the gains in writing that section in another language will be sucked up by the process of binding the two languages together. In a complex app, you might get away with two languages. I doubt you'd see a productivity gain with more, even if your entire team was well studied in each language.

Even if I honestly think that a given language is the "best tool", I don't use that argument, because too many people use it to serve their own ends.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

In reply to Re: "The right tool for the job." by hardburn
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.