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.

use Perl

All the Perl that's Practical to Extract and Report

On the importance of names More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Maybe, maybe not (Score:1)

by grantm (164) on 2004.02.16 1:38 (#28486) Homepage Journal

I have to say I'm torn on this one. On the one hand, I see projects like Apache, and for that matter Perl, which have catchy names that don't aim to be descriptive and it's worked well for them. On the other hand if someone was looking for say an OO to RDBMS mapping framework they'd be far more likely to stumble across Class::DBI than Alzabo. I'm not suggesting the CPAN namespace hierarchy is as good as we can get, but there's certainly plenty of value in it.

Reply to This
- Maybe not. (Score:1)
  
  by educated_foo (3106)
  
  Have you ever tried finding a Ruby library to do X? This convention of cute and clever (rather than obvious) names seems much more common on the RAA, and it causes nothing but pain.

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.