6lang Naming Proposal is Good
I think 6lang naming proposal is Good
6lang: The Naming Discussion Update
I'm Perl programmer, not Perl 6 programmer. People seem to think Perl 6 is successor of Current Perl at first time.
It is strange that Version Number is contained in Language Name. We should admit this idea is wrong.
Perl 5 vs Perl 6 never produce any values. Many misleading occur and it damage Marketing of both Perl 5 and Perl 6.
Both children are damaged for a long time.
In Perl 6
Perl 6 is new language, has new paradigm, features, for example Parallel processing.
But Perl name call in our heart that it is traditional and plain old. Perl is King of script language Backward Compatible. Perl 6 is never so.
New Things need New Name. If old name is used, the value of new things is hard to see from normal people.
In Perl 5
Perl 5 wait to upgrade Perl 7. Ruby became Ruby 2, Python became Python 3, PHP became PHP 7. But Perl is Perl 5 for a long time.
Reset is needed from both perspective of Perl 5 and Perl 6.
Perl 7.0 and 6lang 7.0
If both language start to walk at each way, it is good.
How about Announcement of Perl 7.0 and 6lang 7.0.
I'm Perl Programmer. I LOVE Perl. I want to contribute Perl community and Perl users.
I like Perl 7, but "6lang 7.0" sound silly
Why version 7.0 for 6lang? :) It's already versioned using letters: 6.c for the current one, next one is 6.d, 6.e afterwards, etc.
There's currently not a lot of support for "6lang" as an alias to the language name and not enough support for complete rename away from "Perl 6".
As for "Perl 7.0", doing that right now is somewhat pointless. Without a solid rename of "Perl 6" done first, it's basically equivalent writing off "Perl 6" as a dud. But even if we assume such damage is irrelevant, "Perl 7.0" will be what exactly? Just a "Perl 5" under a different label that implies backwards incompatibility but with no new features to justify a major version bump? Feels a bit dangerous: sawing confusion among current users who don't want breakage due to major upgrade; without gaining any new users due to modernized features.
Such versioning scheme also will see another family member to jump over eventually: Perl 11. I think someone proposed "Pumpkin Perl" in the past as a walk-away from just-Perl name, just as "Perl 6" is trying to do so. Perhaps that's a safer path.
+1
+1
Show Perl 6 code to a non-Perl programmer and let him/her decide. He/She will clearly answer "it's Perl".