I'm a guy with a Camel tattoo who found Ruby and never went back to Perl, but have followed Perl 6 out of nostalgia. Here's the answers as I understand them:
- Version 6.c? Why not 6.0?
This is first, a reflection of the playfulness of Perl, and second, a statement about language design. The first release, an alpha, was 6.a. The second, a beta, was 6.b. The third, the actual 'final' release, was 6....c? Since it was being released on Christmas, and 'c' fits, it was decided that releases of Perl 6 would be named after holidays, and they went back and found them for A and B too.
As for the statement about language design, I'll add that onto the next one, as it makes more sense in that context.
- What's with the whole "language" and "compiler" distinctions no one cares about?
"Perl 6" is a _language_, not an _implementation_. There's a language spec, and any implementation of this spec is a Perl 6. This is a distinction that a lot of projects make, but is a lot fuzzier, because they don't have specs. Consider Ruby: yes, JRuby is also a Ruby, but since there's no language spec, people still assume MRI when you say "Ruby". Perl people don't want you to assume Rakudo when discussing the language itself.
This is why there's no minor version of "Perl 6". Language specifications change a lot less frequently than compilers.
- Why is the first stable release of the compiler not optimized to the max?
Like most projects, as long as performance is Good Enough, it's good to get people start using it, and then work on performance after. Especially for a language where performance isn't a main goal, like Perl. As long as you haven't painted yourself into a corner with language decisions, performance improvement is refinement work.
- Is there a need for a new Perl? What is it good for?
I don't know if there's a _need_, but Perl 6 sure improves on a ton of things about Perl 5. It's the stuff that makes Perl Perl, but turned up to 22, not just 11.
The last two are questions I can't really answer.