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
Here is a suggestion for Perl's branding:
http://nigelhamilton.com/perl-branding-proposal.html
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
On 2018-02-16 11:15 AM, Nigel Hamilton wrote:
Here is a suggestion for Perl's branding:
http://nigelhamilton.com/perl-branding-proposal.html
I like your proposal.
But its details would need fleshing out more, particularly at the end, where it
says this:
Perl $new_runtime_name_for_perl5_goe
> Here is a suggestion for Perl's branding:
>>
>> http://nigelhamilton.com/perl-branding-proposal.html
>>
>
> I like your proposal.
>
>
:-)
> But its details would need fleshing out more, particularly at the end,
> where it says this:
>
> Perl $new_runtime_name_for_perl5_goes_here (tm)
> Perl $n
Marketing is not only about branding. It is also about finding Evangelists.
Perl's traditional base was in
- Web Development,
- Text Processing,
- Bio-Informatics and
- As a general glue language among the sys admin and EDA community.
How many of these sectors are moving away or have