I think your question is an interesting one:

     Do you agree reliability and security must be 1st and 2nd priorities, or not and why?

I must admit, I fall into the 'works for me™*' school of thought -- but I'm open to being gently encouraged or corrected. Your original 'rant' and subsequent posts have not (yet) inspired me to change (mostly because they are long, somewhat rambling, and I don't have a lot of extra time today). I was surprised to see that your initial node is (or was, at the time of this comment) still in positive reputation territory ... because I think you come across as complaining or rebuking but not really offering a solution. Can you succinctly sum-up your arguments for why you think the bar of reliable and secure software should be raised, and how you propose to raise the bar on CPAN or within this community? What solution are you offering?

Most of us are not against producing more reliable and secure software ... but you have to gently convince us that:

  1. we are not already doing so
  2. we (both individually and as a community) will gain something tangible by doing so
  3. there is a workable path to improving in this direction

I'm a very pragmatic person, and I'm generally rewarded by delivering results on a day-to-day and week-to-week basis, which is partly why I love Perl. If I'm going to redirect bandwidth toward more secure and reliable software and away from delivering those immediate results, I'll need some justification.

*works for me = Works within the context of my current environment. Currently, that means I am developing for internal users within the semi-safe confines of an intranet.

In reply to Re^2: Reliable software OR Is CPAN the sacred cow by ptum
in thread Reliable software: SOLVED (was: Reliable software OR Is CPAN the sacred cow) by powerman

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.