If we assume the use of NQP is part of the project's identity, then yes that makes sense. Historically that wasn't the case, eg the earlier Rakudo were written to Parrot PIR directly, and there's the possibility this could change again, though I see that as unlikely. Not a bad idea. -- Darren Duncan

On 2018-02-16 3:07 AM, Lloyd Fournier wrote:
I'm about to publish some blog posts with using Perl 6  to demonstrate some cryptographic primitives. I was thinking about calling it "rakudo" to at least intrigue people and make them google it. Couldn't we call the language rakudo and the implementation nqp-rakudo? (ie a rakudo implementation in nqp)


On Thu, Feb 15, 2018 at 5:02 AM Patrick R. Michaud wrote:

    On Wed, Feb 14, 2018 at 05:55:54PM +0000, raiph mellor wrote:
     > (Perl) Rakudo
     > ===========
     > If jnthn and pmichaud and larry can warm to this idea, then:
     > [...]
     > The 'Perl' could be dropped from Rakudo specific propaganda,
     > calling the language just Rakudo instead, to reinforce that it refers
     > to 6e and beyond. But the Perl could be retained in any material
     > covering both Raptor and Rakudo as a reunified tech / community.

    FWIW, I am VERY MUCH AGAINST the idea of naming a language after its
    implementation.  I've seen the confusion it causes in other environments and
    we ought not repeat that mistake here, especially since we don't have to.

    Whatever things end up being called, don't confuse the implementation(s)
    with the language definition.


Reply via email to