The need of the hour is spec completion, stability,speed, documentation, libraries and tools and not different backends.
Sure, but you can tell volunteers to work on only what you want them to work on until you're blue in the face, and they'll work on what they want to work on.
I have a lot more confidence that Parrot will be the best host for Rakudo for the foreseeable future (and the best mechanism for cross-VM portability) than I do that some as-yet unbegun port of PCT and NQP to another VM, but that governs how I spend my time, not how anyone else does.
In reply to Re^6: Backend diversity for Rakudo
by chromatic
in thread Backend diversity for Rakudo
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |