The cost of a new webapp machine (including all provisioning, bandwidth, sysadmin costs, etc) is generally the cost of 1 week of developer time. The cost of a new database machine (about 4x as powerful) is generally 2 weeks of developer time. If I can write something in 1 week (in Perl) and it requires 2 machines or take 4 weeks (in C++) and it requires 1, I have saved two weeks of my salary. This assumes that the C++ version even does everything the Perl one does and that the C++ one requires half the resources of the Perl one. (Both have proven to be faulty assumptions).

Furthermore, the Perl version is going to be easier and safer to extend than the C++ version. New developers are going to be productive more quickly. And, there is more battle-tested code for Perl (via CPAN) than there is for C++.

The key is determining where your costs are. 30 years ago, the significant cost was hardware, so you optimized for hardware speed. Today, the significant cost is developer time, so you optimize for developer speed. This is the origin of "throwing hardware" at a problem. It's usually the right business decision.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: speed factor by dragonchild
in thread speed factor by hashin_p

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.