develooper Front page | perl.perl6.language | Postings from February 2018

RE: Naming debate- what's the location for it?

Thread Previous | Thread Next
Eaglestone, Robert J
February 20, 2018 15:34
RE: Naming debate- what's the location for it?
Message ID:
Thank you for your insightful comment Vijay.  You’re right.

Perl6’s evangelists will typically be current Perlers who are running up against Perl5’s limitations.

So I think you’ve circumscribed the issue: what is Perl6 for?

  *   Perl6 could be “better than Go” for microservices – IF it’s easy to do that.
  *   Perl6 could be “better than Scala” for concurrency – IF it’s better than Scala at it.
  *   Perl6 could be good for text processing.  But I don’t know how Rules work.
  *   Bio-Informatics would be great – IF Perl5 is limiting their scope and P6 opens it back up.
  *   I am having trouble seeing Perl6 as a sysadmin glue language.

In my opinion, the first evangelists are more likely to be microservice and concurrency coders than enterprise coders.

From: vijayvithal jahagirdar []
Sent: Saturday, February 17, 2018 1:05 AM
To: Darren Duncan <>
Cc: Perl Language <>; raiph mellor <>
Subject: Re: Naming debate- what's the location for it?

CAUTION: This email originated from outside of CA. Do not click links or open attachments unless you recognize the sender and know the content is safe.
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 moved away from Perl? What is the game plan for bringing them back?

  *   How many courses are there today on Coursera or Other MOOCS which use Perl to teach one of the above?
  *   If I wanted to learn something new today, rather than plod through 300 pages of a book I would signup for a course and spend the time in watching the course material and doing the assignments.
  *   When I wanted to learn DataScience, courses using R and Python were readily available. Even though I had been using Perl for 20 years, I did not even know where to start in the Perl ecosystem!

I believe along with re branding we also need powerful narratives about how Modern Perl and P6 are better than their competitors in the selected domains.



On Sat, Feb 17, 2018 at 3:26 AM, Darren Duncan <<>> wrote:
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.



Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About