My last post in response to Vadim's recent post.

Vadim is one of those exploring introduction of P6 in a company that makes
significant use of P5.

> I have a work project on my hands which I wanna implement in Perl6. Yet,
I have an internal framework for such projects written in Perl 5.

I wanted to write a bit about what I think the likely short and long term
reaction of the community will be to your efforts.

I would expect the sort of environment you describe to (continue to) be one
of the most important P6 use cases for years to come. While it looks like
we can not afford to tie P6 to P5, the flip side is that we also can't
forget that this scenario was the primary launching point for P6 and that a
natural setting in coming decades will be alongside P5.

And this should essentially be a showcase scenario. P6 coding in the
context of P5 heritage and code bases is very much a sweet spot in terms of
a likely pool of early adopters and also the initial testing ground for
P6's ambitious polyglot (mixed language) strategy.

----

The current P6 community make up reflects the contemporary importance and
influence of P5. In a recent survey exposed mostly in P6 focused fora, 75%
of respondents said they have "used Perl 5 extensively before finding out
Perl 6". (
https://docs.google.com/forms/d/e/1FAIpQLSdqrrcxTQWuN1ISAvz3j_XkpCCc2AuQw9uKgAhTivxHBFsweg/viewanalytics
)

Anecdotally speaking, attitudes among P6 folk toward P5 vary but are
generally at least respectful.

One example is Zoffix. He's an important driver of P6. He wants P6 free of
any drag from P5. But it's noteworthy that he still sometimes uses P5 to
get stuff done. (Sometimes mixed with P6, eg
https://perl6.party/post/IRC-Client-Perl-6-Multi-Server-IRC-Module#dontwaitup
)

Liz, another important driver, is ultimately motivated by the desire to
sustain and invigorate P6 long enough to do likewise for the overall Perl
community in coming decades. The P5 legacy and its future is as central to
her vision as P6.

In summary, I believe that if you keep a positive, practical and persistent
(multi year) focus on bringing P6 into the mix with a P5 environment, P6
leaders will or at least should have your back.

I'm curious to hear whether this is of interest to you or others.

--
raiph

Reply via email to