in reply to
Re^5: MoarVM update
in thread MoarVM update
Do you think he was wrong?
At the time, yes—but as it turns out, all of the FUD flung at Parrot chased away most of its developers, so his prediction came true. After being told not to improve Parrot (being told not to change Parrot), there was no reason to continue working on it. That's why you can see commits and participation drop off a cliff a couple of months after Rakudo announced yet another NQP rewrite, one designed to remove Parrot from Rakudo's long term plans.
Granted, it's taken a couple of years and Rakudo on the JVM still doesn't pass as many P6 spec tests as Rakudo on Parrot, but I'm confident that they're aiming for feature parity eventually.
So now what?
So now MoarVM doesn't even pass all of the NQP test suite, so let's all stand up and cheer that the Rakudo developers are dividing their attention between three VMs that we know of: one all but dead but still the most feature complete, one proprietary and memory hungry and a black box of sharecropping, and one nascent that needs at least one rewrite and doesn't run any P6 code worth mentioning.
My guess is what next is yet another rewrite of major components, yet another VM announced, and still nothing I can give to customers who expect little things like stability, library support, and documentation.