I started using F/OSS because it is free. Then, I used it because it is good enough (and more) for what I do. Then, I finally understood why I must use it and that is because I can tailor it to what I want.

The version of perl (or apache or mysql) that comes with the OS should be used solely by the OS. The reason RH still ships Perl 5.8.0 (patched heavily) with their OS is because their scripts work with 5.8.0 and upgrading may break that. Installation and maintenance scripts can take a little longer to run, but they have to run successfully.

My highly optimized webapp has very different needs than the OS perl. As such, I shouldn't be screwing with the OS perl by installing additional modules or upgrading stuff. I may break it. So, I ALWAYS compile my own Perl, Apache, and (in some cases) MySQL. I ALWAYS use my own gcc to do these things (largely because I want gcc 4 and the massive improvements over gcc 3.x). And, I ALWAYS put it somewhere else, in its own directory structure and usually in its own jail. And you should, too. Until you've seen an OS fall apart because someone upgraded a CPAN module and you had to fix it at 3am on a Sunday, you haven't lived. :-)

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: blaming perl for not using a build policy by dragonchild
in thread blaming perl for not using a build policy by trwww

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.