Rakudo mostly lacks IO to be a proper superset, as well as concurrency.
Why don't you people get the spec finished before starting to implement anything ?
If you write code while not having a finished spec you're probably writing code that will get deleted on further revisions of the spec so you're basically wasting time.
So why don't the people with a good CS background in the Perl6 team just meet up and finish the spec and then you can start implementing ?
I think (although old) the waterfall methodology of developing software is the best one. Agile is really not good, except for teams of people who really have to rush to get something done(crappy, real-world software), but it is not the case with Perl6 if you say you want to write something good, there should be no hurry involved, just finish the spec already so you can get to the next phases.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||