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.
  • I think the problem you're trying to solve is an important and useful one. In Perl6 it will not be as big of an issue because we will have Roles, so multiple JSON modules can implement the JSON role using whatever backend then like. Although this isn't perfect since some JSON modules might want a completely different interface so they won't provide that Role per-se.

    Maybe we should have something tied to Bit-Card accounts where people can say "Hey this other module does the same basic thing better" then. We could solve the upstart problem just by listing all recoomendations with but with the total number of votes each received and listed in order of popularity. So an upstart will start at the bottom, but will at least be seen.

    And for those who want to leave comments they can be left and for those who want to view them they can be viewed, but the primary view is just a list of the ordered recommendations.
    • You just described cpanratings.

      There's quite a number of comments there that say "This is not very good, use Blah::Blah instead".