Nice!, but

Look, what users want right now, is 1 VM running 100% of Perl 6 features completely, without show stopper bugs, which is fast and with some decent standard libraries and documentation. Not 10 VM's running 10% of Perl 6 features.

Parrot did just fine, and if you felt that was too unstable to die soon or lose support. JVM did equally fine too. JVM in neither dieing, nor will anytime soon. Once you get it right on one VM, you are all welcome to port it to as many as you want

Right now, most users are just hoping against hope that they will see Perl 6 out some how. I know you are going to talk about regular releases, now what good would those releases do but to only test and try language features? Beyond that, what?

Right now the 'Rakudo on Moar VM' hasn't moved a needle on the feature completion matrix, speed, libraries, or documentation. It just ensured you spent more time away from those more important priorities. And you will spend more time porting further features on these multiple VM's. in the future

To be frank I sincerely, just.. again.. hoping against hope.. that in 2014 Perl 6 doesn't suffer a major rewrite, No new big sub-projects started, No new VM's are written, No new effort's to port to existing VM's happen.

As a user I would like to see 2014 be an year with Rakudo being 100% feature completed, a little fast, without major bugs, with decent libraries and documentation. In other words ready for the rest of the world

Happy New Year!

As I understand it, MoarVM was started for a specific reason: it should be theoretically linkable to libperl, allowing it to run Perl 5 modules, including XS modules. That is, it should eventually be able to run most of CPAN.

That seems a pretty worthy project to me.

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

I think the Moar VM project was started because they though JVM wouldn't be a acceptable platform for a lot of shops. So they wanted to roll out their own one.

Either way, Its importance can't be denied in totality. But in the long list of priorities, that's may be the last project to execute once the implementation of the existing spec is done.

Moar got started because Rakudo hates Parrot. Rakudo already had a code to embed Perl in Rakudo on Parrot. That was called Blizkost or something. I guess they threw away that code too. The other AM is right. This is a project that can't finish anything.