3 ms·

I don't think it's fair to characterize Rakudo Perl 6 as incomplete, at least on the MoarVM backend. It is very nearly complete, with the bulk of the semantics

by labster 11y ago

I don't think it's fair to characterize Rakudo Perl 6 as incomplete, at least on the MoarVM backend. It is very nearly complete, with the bulk of the semantics fixed in years past. It is currently passing 122627 tests[1]. If you write code today, it will probably not break by December. I guess it still counts as unstable software, but I used Gmail beta for half a decade and that turned out fine. At this point, its a matter of nomenclature, because I've certainly used buggier "final release" software. [1]: https://github.com/coke/perl6-roast-data/commit/2aeeb87edc https://github.com/coke/perl6-roast-data/commit/2aeeb87edc

dragonwriter 11y ago
> I don't think it's fair to characterize Rakudo Perl 6 as incomplete, at least on the MoarVM backend. Look, I think Rakudo Perl 6 is great, and its quite usable for many things. OTOH, I think it is quite fair to refer to it as "incomplete", because: > It is very nearly complete "very nearly complete" is a kind of "incomplete". You can't really make a fair comparison to Perl 6 uptake before even the Perl project is calling Perl 6 "ready" with Python 3 uptake 7 years after PSF said Python 3 was ready.