First Point:Reliability and securtiy mean different things in different contexts to differnt people. Depending on the different modules, no that isn't and probably shouldn't be the first goal. If a module is reliable and secure but unusable what have you gained?

Second point: Module authors goal match the goals of the project they were developing when they decided to code the module. Which normaly falls in the "get it done" category along side the "works for me" category. These don't mean the module wont be secure and reliable, it simply means that the level of security and reliability will match the goals of the project, not some preset goals for releasing software.

Final Point: If cpan was started with only "secure" and "reliable" modules with no room for immature modules then you significantly raise the bar of entry. People who would have published modules would not have, they wouldn't have learned and grown an we wouldn't have the better modules they latter produce or the modules inspired by their first attempt. CPAN and perl would be poorer for the loss not richer, at least that's how it looks from here.


___________
Eric Hodges

In reply to Re: Reliable software OR Is CPAN the sacred cow by eric256
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.