Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • First, I'm glad to see you doing this sort of thing. Automated CPAN analysis is good to have. I'd like to correct a few notes on the Phalanx 100, though. First, consider why the Phalanx 100 was created. The Phalanx project was an attempt to increase test coverage in the most-used modules on CPAN, so that Ponie would have a good test base to work with. The Phalanx 100 was created by analysis of CPAN download logs for a one-month period from one mirror. We figured that would be a good enough estimate of


    • At the time that the Phalanx 100 was created, my specific beef was that it didn't appear to factor in dependencies.

      So while we got a list of 100 modules, they weren't ACTUALLY the most 100 used, just the 100 most in some other sense.

      I do, however, appreciate that they were based on usage data, as opposed to dependency data. And I totally plan to start factoring that into some of the indexes, once I've got the basic naive ones working.

      • I guess I take issue with your "beef" because it was never intended for your use. We didn't make any assertions as to how the data should be used, so it's not fair for you to say it's not what you want.

        Our feeling on dependencies was that dependencies would have to get downloaded, too, and so those downloads would show that traffic. So you get dependencies in that data, but not weighted by the number of other modules that use the dependency. A single-use dependency would get as much weight as, say, HTM



  • Now that would be a perfect list for testing a CPAN packaging system...
  • I have some equivalent tools that crawl the packages themselves. I just ran my dependency chain tool for MojoMojo and come up with 239 deps rather than your 266. I'd be very curious to see what the discrepancy is.
  • It would be good to have a few different measures of module popularity. Personally, I think a listof the "most depended on" modules would be really useful. That some other module author would use a module I think is a pretty good vote of confidence for the usefulness and quality of that module. Such rankings would especially help when trying to choose between roughly equivalent modules for a project.