Posted Mar 17, 2010 17:02 UTC (Wed) by chromatic (guest, #26207)
In reply to: Parrot 2.2?? by kragil
Parent article: Parrot 2.2.0 released
Perl 5 and Perl 6 both are under active development, and that will continue as long as people are willing to work on both projects. (You try predicting what volunteers find interesting.)
If you want to use Parrot in production, feel free! It's been in distros for a while. I can't give you a list of exactly who uses it and for what because that information's not visible to developers.
The current Rakudo plan is to have a big release at the end of April (modulo any schedule changes due to real life intruding on its lead developer) intended for end users. Like Parrot, Rakudo has had regular monthly releases since January 2007, each one better than the previous. Whenever you find that one of those releases meets your needs, you're very much welcome to use it. We tend not to believe that there's a single version that is the point where everyone should use it for everything, and we encourage you to make your own evaluation.
Posted Mar 17, 2010 17:24 UTC (Wed) by b7j0c (subscriber, #27559)
[Link]
awesome, i hope the april release coincides with some good documentation, because its not clear to me what is or isn't supported out of the synopses, which i presume have not changed since their original authoring
Parrot 2.2??
Posted Mar 17, 2010 17:59 UTC (Wed) by chromatic (guest, #26207)
[Link]
The Synopses reflect the current design of the language; they get updated frequently, based on feedback from the multiple Perl 6 implementations under active development. If you skim them, you'll get a good understanding of the design of Perl 6.
With that said, the Rakudo book is also under active development. We'll publish it to coincide with the Rakudo Star release. It'll introduce the Perl 6 features supported fully in Rakudo Star.
Parrot 2.2??
Posted Mar 18, 2010 5:01 UTC (Thu) by sitaram (subscriber, #5959)
[Link]
[hardcore perl fan here...]
> We tend not to believe that there's a single version that is the point where everyone should use it for everything, and we encourage you to make your own evaluation.
For me, it's a question of unlearning/relearning new features that are in flux. I wish someone would say "right... this version does these things, which will not change, be re-thought, or be re-designed. More features may be added but these *will* stay as they are".
In other words, I'm not holding off because the software is not stable, but I am looking for stable *semantics*.
[I also realise it's been a while since I tracked perl 6 closely enough to know if that is still a problem; apologies if not -- just correct me right here please!]