I doubt if a master list would actually add something that http://search.cpan.org doesn't already provides. You would get a huge list, that eventually you had to dig through.
Now, if you want to know what module to use, if, for example, you want to do some form validation, you might as well search CPAN directly with "form validation". Besides that, CPAN also lists it's modules category-wise, so if you aren't sure what exactly you want to search for, that might help.
| [reply] |
Seems like a module list would be subject to controversy. Of course, some modules are better than others, but in many cases they are simply different -- as different as English and Outer Mongolian.
For instance, if you like POE you might favor POE modules over non-POE ones. This is a case of style preference dictating module choice. In other cases, functionality dictates choice. I find POE very interesting, but Net::Jabber floors POE::Component::Jabber in terms of current functionality. So in this case, functionality might drive the decision. Still, I think there is a reasonable debate that in some cases both the POE version and the non-POE version have their uses!
A very wise Philosopher once said "There are two roads to go by, but in the long run, there is still time to change the road you're on." Try to not let the choice of modules dictate your application's permanent direction. Isolate them to the side, if you can, you may find better ones. It appears a good chunk of learning Perl is learning which Perl modules are cool, and cooler ones come along all of the time.
| [reply] |