comment on

And still today the Perl community hasn't defined a clear future

I'm not sure what he means by this. My best guess is a perceived lack of a series of "5 year plans" stating what changes are planned, for which releases and when those releases are scheduled.

Perl is maintained (mostly?) by unpaid volunteers. Maybe Python, Ruby, etc - whatever is touted as being "the future that Perl won't have" - have corporate backing that Perl doesn't have. Or, maybe the people maintaining them are more like the (highly paid) "MS Project Jockies" that manage projects for big corporations. I don't know.

I think what's most damaging to Perl is commentary like what the OP quoted. Unfortunately, I don't know how to counter it.

Update: Radical idea: Drop the "5" and call the next major release "Perl 28.0". (except, Larry won't allow that)

In reply to Re: Tiobe index - Perl is having a hard time by RonW
in thread Tiobe index - Perl is having a hard time by reisinge

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