The only purpose for this thread is to capture and vote on proposals for a new name for "Perl 6" to help with alias name decision during 6.d release. PLEASE NO DISCUSSION, just names and vote on them. I have added "Perl 6" (i.e. no rename) as an option. If you want that, upvote it.

I suspect the community stands ready to promote the alias to a full rename by acclamation if it is any good at all. I for one hope I never again recite "No, no, no, it looks like it has the same name but it doesn't because that's not a version number (anymore), really it's a whole other language (similar one though)."

In Perl 5 land, it has been a big, constant problem that Perl is defined by perl. Larry wants to keep far away from that this time. (So do some other people who don't get the last word, but Larry is reason enough.)

I understand this history. And given the context, probably that was a smart decision to make too. However, after years of reality and fail to re-assess the decision, that questions the wisdom. Often in history, the correct path is somewhere between that takes some back-and-forth to figure out. Sticking one way or another, (for decades?), that is near stupidity (every wise man is allowed to have some stupidity).

In the actual assessment, Perl 5's latest revisions has managed large part of backward compatibility while correcting and adding behaviors. So to be fair, Perl hasn't been entirely defined by particular version of perl for quite a while now.

As for the name, a C compiler is called cc, or clang; a java compiler is called javac; a python compiler is called python. There is nothing unusual to have a rakudo compiler called rakudo; it is very normal when that compiler is the only game in town -- what is so wrong calling search "google"? It won't supress competition for sure. What matters is reality not ideaology. When there is competing compilers, what is the language and what is the compiler will be clear. When there is only single player, the distinction has no practical meaning.

"All sheep are purple" is not an abstract idea. It is a concrete one. An assertion of fact. Do you not know the difference between abstract and concrete? Here is a hint: they are opposites. Your analogy is not valid.

A more appropriate analogy would be if I had said, "sometimes sheep don't look white" and you said "but there many white sheep". You haven't proved or disproved anything.

If P++ is even infinitesimally more difficult to Google than another name, and you cannot prove that it's not infinitesimally more difficult, then I am correct.

Interesting you added a caveat, the "if the name catches on" part. And if it doesn't? Seems like you agree with me whether you like it or not.

I'm not going to delve into some logic war. That's simply a red herring.

When I said "if the language catches on" I meant to say "If it gets approved as the official name." I admit my mistake. Cool.

Having said that, the matter of the fact is that, if P++ is decided to be the official name, then it will not be hard to google it given google's proven record of effectiveness with those types of searches. Whether it's "infinitesimally harder than some other name, like Perlkablamo," is besides the point.

YamaScript, just yama for the CLI invocation. Where Yama is a god in many eastern cultures including vedic and buddhist related ones. He's depicted with six limbs and the sanskrit of the name means "twin", riding a water buffalo (we can make it a camel right?). In charge of death and controlling the cycle of rebirth.

I wonder how Larry feels about all of this. I know you don't want any discussion, but I think his comments on this situation would provide some valuable insight. I'm just a Perl 5 programmer. As cool as Perl 6 is I haven't done much with it at all, and am not very confident my input will have considered the Perl 6 side of things

Well that about settles it for me. I don't have the expertise to contribute to the sort of modules that would make using Perl 6 a reality for me, but if it ever gets to the point where I can develop real world web applications easily and reliably the same way I can in Perl 5, I'd be happy to invest as much time as possible in porting my application logic over. But until then, I'm going to have to stick with Perl 5 as my language of choice

I read that Perl 6's DBI equivalent wasn't up to par with Perl 5s and that's what's been steering me away the most. I need to able to reliably interface with a SQL database if I'm going to use Perl 6 for anything serious web related. Also performance is an issue, but I'm more confident that will sort itself out overtime (if it hasn't already)