I'm happy to revise my decision if you can come up with several examples that illustrates where the Perl 6 designers are ignorant of prior art.
You're drawing a very fine distinction between somewhat disjoint groups: Perl 6 designers, Perl 6 implementors, and Parrot implementors. Outside of #perl6 and perhaps #parrot, no one cares about this distinction. In truth, that finger pointing is one big reason for my disillusion with the whole thing.
I know, but I expect better from somebody who calls himself "educated", has contributed to the VM and arroaches to call the involved people "ignorant".
I also honestly don't see why that distinction is so hard to grasp. After all C is also a language, and there are many well-known compilers (GCC, MSVC, ICC, ...), and most programmers are aware of that fact.
Okay, let's try to be "technically correct" (the best kind!).
I'll choose my favorite C or Java compiler -- you choose your favorite Perl 6 compiler. Does it do profile-guided optimization? Polymorphic inline caches? Real-time garbage collection? Can you even explain these things? Yeah, I didn't think so. Please see GCC and Sun's Java for prior art.