NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Reduce the number of CPAN modules (Score:1)
I agree the 10000 modules is an impressive count. But wouldn't it be a worthier goal to decrease the number of modules? I guess that there are a lot of redundant and abandoned modules on CPAN.
On the other hand, I'm wondering about refaktoring. Does refaktoring tend to increase the number of modules, as large chunks of code are broken up into smaller pieces? Or does it decrease the number of modules, as cut&past code is unified?
/* Bernhard.Schmalhofer@gmx.de */
Re:Reduce the number of CPAN modules (Score:1)
I've personally deleted 2 in the last 3 months. One was just an idea that had since been solved a different way, and the other was a bad mistake that never even ran.
But why delete anything?
If something is abandoned, who's to say it isn't still in use?
We get people emailing the modules@ mailing list asking to take over modules about once a week or so.
And if something is redundant, should we abandon all the current users?
Some things get deprecated, but even then they stay in for compatibility, and just get flagged (DEPRECATED) in the module ABSTRACT.
Refactoring of big modules, does often see them split up. And occasionally merged together. It seems to be a bit of each.
Reply to This
Parent