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
use Perl Log In
Thursday July 23, 2009
07:09 PM
Gems driving me to drink
I don't know my blood pressure but I'm considering getting a desk-side monitor just to empirically know when I'm being driven out of my mind.
I wish:
- that Ruby's RubyForge had something like CPAN's browseable directories like http://cpan.org/modules/by-module/Test/ for finding related things all grouped together
- that Ruby's gems were named categorically instead of "Bob's Unit Testing Framework"
- that there was a search.rubyforge.org which worked at least as nice as http://search.cpan.org/
- that I could find where the test reports of gem's tests are aggregated like the CPAN Tester's http://matrix.cpantesters.org/?dist=Test-Simple+0.92
Work day's done now. I feel ill.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
other reasons to hate gems (Score:1)
there is one relatively nice feature. running a local repo is as easy as typing gem server
Re: (Score:2)
Might not be a good idea: http://blog.urth.org/2009/05/the-real-problem-with-dependencies.html [urth.org]
They can be run explicitly, though. And, they can be run after they're installed. I don't know how to do that with cpan.
You can add github as a gem source so it will automatically look there.
I repeat, you can add a source. And that's not an issue
Re: (Score:1)
mostly i blame developers for wanting new shiny things.
Re: (Score:1)
Might in fact be a better idea than so far thought [dagolden.com].
What a gem... (Score:1)
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.
Re:What a gem… (Score:1)
It’s a rock star culture.
Rubygems (Score:1)
Re: (Score:1)
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...