Re: Future Directions for Parrot and Rakudo

2013-06-24 Thread Allison Randal
On 06/24/2013 04:34 PM, Darren Duncan wrote: So you're saying then that Jonathan's post wasn't an official statement from the Parrot dev team after the group decided what to do? It certainly read that way to me. Jonathan's statement on parrot-dev was the first I heard of it, and as far as I

Re: Future Directions for Parrot and Rakudo

2013-06-24 Thread Darren Duncan
On 2013.06.23 8:43 AM, Allison Randal wrote: On 06/21/2013 10:07 AM, Jonathan "Duke" Leto wrote: Howdy, The future of Parrot and Rakudo Perl 6 are on divergent paths. I am dedicated to a successful future for Parrot which is independent of Rakudo Perl 6. As soon as Rakudo Perl 6 works on Moar

Re: Future Directions for Parrot and Rakudo

2013-06-24 Thread Jonathan "Duke" Leto
Howdy, The code must flow. I will not force decisions on anybody, but I intend to continue on my path. If it is not for you, I implore you to find your own. Duke On Sun, Jun 23, 2013 at 8:43 AM, Allison Randal wrote: > On 06/21/2013 10:07 AM, Jonathan "Duke" Leto wrote: >> >> Howdy, >> >> The

Re: Future Directions for Parrot and Rakudo

2013-06-24 Thread Allison Randal
On 06/21/2013 10:07 AM, Jonathan "Duke" Leto wrote: Howdy, The future of Parrot and Rakudo Perl 6 are on divergent paths. I am dedicated to a successful future for Parrot which is independent of Rakudo Perl 6. As soon as Rakudo Perl 6 works on MoarVM (the spiritual successor of the m0 branch i