comment on

I notice that all the best perl resources are antique, broken, and unmaintained - lagging well behind all competition for some time now.

Perls strongest asset, CPAN, sits mostly abandoned; it's polluted with junk that doesn't work, with nobody wanting (or allowed) to fix anything, useless search, no statistics, no way to comprehend what might be "mature" versus what's an incomplete shell of worthlessness, an interface from the stoneages, and simply horrific security concerns.

Perl itself doesn't even exist and any of todays most popular devices! (and yes, by "exist", I'm not coutning the dedicated hackers who've violated warranties or dedicated weeks to somehow shoehorning something into their own personal device. If it's on less than 0.001% of phones/tables/whatever, and/or used by 0.000 of applications out there - it doesn't exist)

I'm going for "1st July 2011" as the official day that perl finally died.

R.I.P.

In reply to What was the date that perl actually died? by cnd

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.


go ahead... be a heretic
	PerlMonks