Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If CPAN::Reporter becomes more widespread, then one way authors will get a sense of usage is to see how many test reports have been submitted against their modules. It's far from perfect, but it's another data point for how often a module gets installed relative to others. I quite enjoy watching my CPAN Testers RSS feed just to see what's been tested lately.

    Ditto for CPANPLUS, of course, but it's less commonly used than CPAN.pm.

    • Sorry to split hairs, but the OP was talking about how many people are *using* a module, while you are talking about how many times a module *was installed*. Two *very* different things... :)
      • I know. I said "get a sense of usage" and "far from perfect" to indicate that. Likewise, complaints about breaking a module doesn't really say how many people are using a module, just how many people (a) upgrade to the latest release and (b) report breakage.

        Short of sending a "phone home" packet whenever a module is loaded (which would be very naughty!) -- there's no real way to know about usage. Even the Phalanx 100 is based largely on download counts, which implies but doesn't equal usage.