4 ms·
Re: There is a balance between completely abandoning old users (e.g. Perl 5 to Perl 6) Please note that Perl 6 has been renamed to Raku (https://raku.org https
by lizmat 7y ago
Re: There is a balance between completely abandoning old users (e.g. Perl 5 to Perl 6)
Please note that Perl 6 has been renamed to Raku (https://raku.org https://raku.org using the #rakulang tag on social media).
In the original design of Perl 6, a source-level compatibility layer ("use v5") was envisioned that should allow Perl 5 source code to run inside of Perl 6. So the plan was to actually not abandon old users.
In my opinion, this failed for two reasons:
1. Most of Perl 5 actually depends on XS code, the hastily devised and not very well thought out interface to C code of Perl 5. Being able to run Perl 5 source code in Perl 6 doesn't bring you much, unless you have a complete stack free of XS. Although some people tried to achieve that (with many PurePerl initiatives), this really never materialized.
2. Then when the Inline::Perl5 module came along, allowing seamless integration of a Perl 5 interpreter inside Perl 6, using Perl 5 modules inside of Perl 6 as if they were Perl 6 modules, it basically nailed the coffin in which the "use v5" initiative found itself already in.
And now they're considered different languages after the rename to Raku, dividing already limited resources. I guess that's the way of life.
- reggieband 7y agoI think my wording "abandoning" was more inflammatory than I would have liked. And I didn't want to call out or target Perl 6 / Raku. What I meant to convey was that the language team behind Perl 6 (as it was known before the rebranding) made a decision that it would be a new language and not an evolution of the existing language. It was the first example in my mind, one most people would recognize, that anchored one side of the continuum I was describing. I assume there are better examples (or worse offenders) but I don't know of any off hand.