Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (3)
As of 2022-08-16 00:52 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?