in reply to Re^6: RFC: How to Release Modules on CPAN in 2011
in thread RFC: How to Release Modules on CPAN in 2011
There are others who would like to see Perl attract a wider audience that included non-programmers, developers who think build is a GUI button, and people who just want drop-in functionality on their website or desktop. If this is a goal, making make a prerequiste to downloading CPAN modules is an impediment. You don't need make to write Perl programs. You don't need make to use Perl programs. You don't even need make to copy scripts from one place to another nor to run tests, so why require it? It is like insisting that everyone who wants to eat cheese go out and buy a diamond cutter. It doesn't make the cheese taste better and it gets in the way of eating cheese.
++
I STILL find it hard to install modules (at leas on Mac OSX Snow Leopard). While I'm definitely new-ish to Perl, I don't consider myself a 'point and click' GUI end user and yet installing modules remains a skill I painfully lack. Quite honestly I don't see how installing modules through the command line makes me a better Perl programmer. (but maybe I just don't know enough about Perl to even answer that)
I would love to see at least an option given to CPAN devs to create an 'easier' install process. The CPAN is always touted as one of Perl's greatest strengths and yet it has this hurdle that newbies (and even not so newbies) need to surmount in order to benefit. I just don't see how that's a good thing.
P.S. Sorry for the rant. It's not something I usually do but this hit home for me a little. Congratulations on the tutorial. Great work!!
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^8: RFC: How to Release Modules on CPAN in 2011
by Anonymous Monk on Jan 11, 2011 at 02:48 UTC |