in reply to How Many Modules Is Too Many?

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.

Developing a module or any software for hire is different. In that case, whoever is hiring you should give you the specifications, and maybe you would need to cut down on the unneeded features and excess file operations.

Replies are listed 'Best First'.
Re: Re: How Many Modules Is Too Many?
by BigLug (Chaplain) on Jun 01, 2004 at 00:21 UTC
    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
[reply]
      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)

      I'm under no moral obligation to maintain my code. I do (as time permits) but I'm certainly not under obligation to. The openness of CPAN is in my opinion the core reason for its success. I'm in total agreement with Jarkko's The Zen of Comprehensive Archive Networks when he said:

      Code quality? Ratings/reviews? Moderation/metamoderation? "Approved" SDKs? These all are hotly debated subjects and will not be addressed here since the CPAN is and will stay an open and free forum, where the authors decide what they upload. Any further selection belongs to different fora. Besides, adding any rating or approval processes creates bottlenecks, and bottlenecks are bad.

      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.

      This is of course your privilege and CPAN allows you to do this. I'm happy using some older modules because they do the job and CPAN allows me to do this too. I don't want to see them go just because they don't fit your usage pattern of CPAN.

[reply]

In Section Meditations