No such thing as a small change | |
PerlMonks |
Re^6: MoarVM updateby curiousmonk (Beadle) |
on Sep 13, 2013 at 07:30 UTC ( [id://1053854]=note: print w/replies, xml ) | Need Help?? |
Rakudo Perl 6 on Parrot is too many years away from being sufficiently ready.
This is the most disappointing thing I've read all day today jnthn decided Perl 6 on JVM was the quickest way to get Perl 6How quick? Seriously speaking I don't care if Perl 6 runs on a dozen VM's in its first 6.0.0 release. In fact I prefer it rather doesn't. There are plenty of other important things like the standard library, CPAN compatibility and documentation to be sorted out and standardized before we branch out to other platforms. Perl 5 doesn't run on any VMs apart from its own and we are perfectly fine with it and its perfectly usable. There is no reason for any one to expect anything other wise for the first cut production release. And not just Perl, most new languages that come today run only on one VM, and users are perfectly fine with that. Perl 6 on JVM might be a decent choice for driving the Perl 6 specification to 6.0.0, and might even be workable for some JVM fans, but it's obviously inappropriate as the only serious VM option. So now what?Far more important than a few percentage of users who can't use JVM or Parrot or whatever are the vast majority of users who would prefer a working product on anything. And by this definition and strategy whom would you please? There are always going to be users, who can't deploy a compiler on a particular VM. So will we keep starting new projects and never finish them. You can release 6.0.0 product on any VM, then you have all the time in the world to release it on other VM's when you want. Other wise no matter how great the progress is in the sub projects, there is hardly any reason for anybody to care.
In Section
Perl News
|
|