I quite agree that one of the most important factors for choice of language is having the technical resource (now and in the future) to write and maintain in it.

Unfortunately (as I rant quite frequently) a very large proportion of IT managers (at a decision making level at least) have little or no technical understanding. As a rule they are appointed by business managers, following the age old adage of 'appoint someone as much like me as possible' (this approach is well attested in org psychology BTW).

They therefore make the decision of what language(s) to mandate in house, often on an entirely non technical basis, based on: the advice of their employees (which they will rarely listen to), the business tech media (what's todays buzzword folks?) and salespeople (Always trust the advice of someone with a personal interest in your decision < /sarcasm>). The result is usually that the choice of 'the right tool for the job' is constrained by available resource, which is in turn constrained by what has been mandated as the 'house language', often for entirely non technical reasons.

--------------------------------------------------------------

"If there is such a phenomenon as absolute evil, it consists in treating another human being as a thing."

John Brunner, "The Shockwave Rider".

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