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.
  • 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
    • You just described cpanratings.

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

    • I don't know about that, but I *would* like to see a scoreboard of the most used modules. Perhaps DrHyde's could extract that information from his cpandeps tool.
  • If we had this already you'd know that JSON::XS rocks much more ;-)
  • In the same frame of mind, there's an idea I've been toying with for some time... It's not rare to have the music instruments used by a band listed in a CD booklet. As programmers aren't that different from rock stars, it'd be nifty to be able to do the same thing. I mean, if Nick Krachmeister can say that he's playing exclusively Howling Kitty Stratocasters then, by Joves, I should be able to say that I use XML::LibXML to craft my masterpieces! :-)

    The implementation could be as simple as putting a file

    • That idea has been tossed around for years. The JFDI suggestion was for people to upload personal bundles (ie. you’d stick Bundle::YANICK in your CPAN directory). You don’t need a lot of new machinery to accommodate that. But we’d probably need a web interface or something to make managing that bundle very easy before people will do it in significant numbers – or at the very least it would need to be widely advertised as a social convention among module authors.

      • Hmmm... yeah. I didn't think about it, but piggy-backing the Bundle:: mechanism isn't a bad idea at all. All that is needed after that is a back-end mechanism that harvests that information, and a snazzy web interface to display the results.

        Well, looks like there's one more cool project I have to throw at the top of the Holiday Hacking pile.:-)