I assume your second whiteknight link was meant to be this[1]. It's interesting comparing his view of Parrot with yours. He may share some feeling with you about Perl 6, but it appears his conclusion about why Parrot didn't work out is quite different. It appears he goes out of his way to explain that Perl 6 did what it had to to get past Parrot's failings:

The P6 folks were developing their own bindings which used the (much nicer) 6model and the (much nicer) P6 native bindings instead. After a while I had to ask myself why I was fighting in the weeds so much, when the P6 people were rising above the problems of Parrot and doing things better? If my writing these things wasn’t helping anybody, why bother with it?

Notice that the P6 folks were having their biggest successes when they bypassed Parrot, which isn’t exactly a roadmap for synergy and mutual success.

He goes on to say he doesn't really like Perl 6, and doesn't believe in it's direction or that it can achieve it's goals. That's fine. Nobody has to like everything.

I have to say I agree with his assessment that Parrot's goals have largely been met by multiple other projects at this point. This post has convinced me even more that not relying on Parrot was the right choice, which is sad because I was a big fan for many years. Parrot was a train wreck. Some people think Perl 6 was or still is a train wreck. But that wreck has been making progress, and may actually arrive at the station. Can the same be said of Parrot? Can you really lay all that blame, or even a majority of it on Perl 6? If people wanted to work on Parrot, they would.

1: http://whiteknight.github.io/2015/01/15/parrottheend.html

Thanks for sharing. I never knew you were so involved back then or that people were being treated that way