in reply to Re^3: Production Perl6 in early 2010?
in thread Production Perl6 in early 2010?
I see. I kind of figured if you had production parrot it would imply production rakudo. I guess I was wrong. I do see your point on why that needs clarified.
But I don't see your point on why it is good to call the different parts completely different names. I'm fine with calling things the "Perl compiler", "Perl interpreter" or "Perl VM". It's the same naming method as every other language I know. When you run it with just one command it really doesn't make sense. Right now, I type perl somescript.pl and I only deal with one program.
I'll admit that I haven't kept up well with Perl 6, but I'd be surprised, and somewhat disappointed, if it's any harder to use than rakudo somescript.pl or whatever the program I see eventually winds up being called. I didn't think we would have to do something like perlc stuff.pl; perl stuff
So yes, they are different pieces and can't be talked about the same, and that makes sense. But in the end it'll all be Perl6.