in reply to
Re^6: Perl 6 and performance
in thread Perl 6 and performance
Even if you find people who want to fix that, it takes forever to fix that when you have to support great wads of buggy, awful C code written as proofs of concept and somehow covered under a poorly conceived deprecation policy, which happens to be self-reinforcing behavior, because if you can't fix things fast enough to support downstream users, they'll write even more buggy and awful C code to poke in the internals, and you have to support that too.
Hasn't the deprecation policy problem been addressed? Namely, that fixes that need to be in can get in faster now?