Wassercrats:
Cpan modules are like free software, so I wouldn't say that any of them aren't good enough. I don't think programmers should waste their time perfecting a module as if it were a tool that they were paid to create. Once they create something useful, they should publish it, and if they want, they or others could improve it as they see fit, at their own convenience.
I disagree completely. CPAN modules are free software, however they're published. People who publish software to a public archive are under a moral obligation to either maintain their code or to remove their code from publication (or, in the case of CPAN, add a prominent note to their documentation that the module is no longer maintained by the author and may be up for adoption)

... or others could improve it as they see fit ...
Unfortunately there is no ability on CPAN for maintenance by anyone other than the publisher. Thus it is the publishers sole responsibility to keep the module working. It is up to them to adopt functionality change submitted by users.

Now, given that, there are too many orphaned modules on CPAN. Personally I don't use a module that hasn't been touched in years. Of course that could mean it's perfectly stable, however I don't feel that is often the case.

Also, I never require a module in another module that either has dependants that are orphaned or that don't pass their tests easily. If I have problems installing something, then I can only assume my users will have the same problems.

"Get real! This is a discussion group, not a helpdesk. You post something, we discuss its implications. If the discussion happens to answer a question you've asked, that's incidental." -- nobull@mail.com in clpm

In reply to Re: Re: How Many Modules Is Too Many? by BigLug
in thread How Many Modules Is Too Many? by Belgarion

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.