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.
    • tests not run by default when you install
    • lots of gems now on github and dont make it to rubyforge
    • people have personal gem repos which you have to use sometimes.
    • up until gem1.3 installs would use a gig of ram.

    there is one relatively nice feature. running a local repo is as easy as typing gem server

  • It would have to be named "Robby's Runit Resting Ramework," since all Ruby modules have to follow the cutesy Scooby Doo naming convention. To me, the Big Suck of gems is the fact that it's not just a package installer -- it also has to be loaded every time you run a script using a package installed via gems, slowing down your script. Ruby copied some things from Perl, and improved others, but totally botched its version of CPAN, Perl's biggest asset.

  • Just wanted to add that you should add gems.github.com as a rubygem source, very handy!
    • I'm mirroring rubyforge and github's gem stream now. I figure I can build something afterward to add categorical information so it's browseable.

      Of course I'd *done* if I were using perl...