Your thesis not new, however it is not entirely without merit. Yes Perl6 is still not at 1.0. Yes, perl 5.10 languished for an extended time, seemingly unmaintained at a critical time in the development of the dynamic web.
Whatever. Those decisions were made and those actions were taken by people doing what they thought was the best thing to do at the time. Maybe they were wrong. Maybe they were right. Maybe somewhere in-between... One thing is certain, stuff happened, it is in the past and won't change.
As to your criticism that Perl6 has no merits or particular strengths beyond Perl5, I can only assume that you have read only this example of Perl6. Had you read any of the excellent, rapidly evolving docs at http://doc.perl6.org, you would realize that Perl6 has some really nice features.
I've been barely dabbling in Perl6 for a few months, and the things that stand out to me are:
- Lazy lists - when combined with nice list comprehension syntax and metaoperators you have immense expressive power.
- Gradual typing - be strongly typed or be dynamic without having to mess about with templates.
- UTF8, I hate it, but Perl6 does it well.
- Concurrency - Perl6 promises, channels and supplies combine with auto-threaded list filters make parallel programming much easier.
On the down side:
- it really is a new language and a big one
- Holy crap, there are a billion operators
- What slurps where and when?
- occasional bits don't work as documented, or are only documented in a Synopsis.
- Rakudo codebase is moving really fast. Of course that velocity is a sign that Christmas may actually happen this year.
I suggest you actually give Perl6 a real try.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.