comment on

I'd estimate that on average...

That's not scientific rigor.

... serious shortcomings. Ranging from...

That bucket lumps together a lot of categories. Some of them are even damning.

... the blanket acceptance...

You're putting words in sundial's post.

... does Perl far more harm than good.

That conclusion is difficult to support.

... cpan ‘is’ probably the greatest concentration of freely available, quality open source software there is...

Seems fair to me to assume that a software professional will use professional judgment to decide what to use and when, and which of your identified shortcomings matter in any given set of circumstances.

In reply to Re^3: Top 11 (GOOD) reasons not to use someone else's Modules by chromatic
in thread Top 11 (GOOD) reasons not to use someone else's Modules by miketosh

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks