Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

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

The point, as I see it, is that open source is a possible starting point in the journey of software development.

No one's obligated to use open source. You are welcome to write your own stuff from scratch if you want. For me, however, open source is a heck of a good place to start, and I accept the reality that something I get from CPAN may not be complete, or bug-free, with the knowledge that I can make a difference by helping improve the module I'm using.

And that's an important difference. I can make a change to Template::Toolkit if I want, for example. If I find a bug, contact the authour/maintainers, talk with the folks in the community, offer the patch, how can that not benefit everyone? I get something that works 1% better. So does the community.

As everyone donates their 1%, we get a better and better product, and build a stronger and stronger community. Many eyeballs make for shallow bugs, and all that.

Instead of fellow monk powerman ranting about how poorly the Mail::* modules fare in following the various RFCs and in security and reliability, I believe s/he should concentrate their energies on making it right.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

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

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?

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

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (2)
As of 2022-08-16 02:13 GMT
Find Nodes?
    Voting Booth?

    No recent polls found