Front page | perl.perl5.porters |
Postings from June 2020
Re: Announcing Perl 7
Thread Previous
|
Thread Next
From:
Christian Walde
Date:
June 26, 2020 20:12
Subject:
Re: Announcing Perl 7
Message ID:
op.0mt43fxpydyjqt@xenwide.vpn.udag.de
On Fri, 26 Jun 2020 21:59:42 +0200, Sawyer X <xsawyerx@gmail.com> wrote:
> On Fri, Jun 26, 2020 at 10:55 PM Christian Walde
> <walde.christian@gmail.com> wrote:
>>
>> On Fri, 26 Jun 2020 21:42:30 +0200, Sawyer X <xsawyerx@gmail.com> wrote:
>>
>> > You say "New users add 'use v'" and I say "Old users update
>> > or add 'use compat::perl5'". The same idea of adding lines of code,
>> > just the question is who.
>>
>> I don't have a particular position right now, but my brain's giving me this to wonder. When i try to think of risk scenarios, this one comes to mind:
>>
>> A perl7 user might not be able to use, say, 50% of CPAN, meaning they can't *rely* on it at all, meaning the singular and overwhelmingly powerful feature of perl is gone.
>
> What this tells me is that we didn't clarify enough how the module
> compatibility that we will offer modules on CPAN will work. We have
> indeed thought *a lot* about not breaking CPAN. It's difficult and we
> won't cover 100% (nor should we) but we did come up with mitigating
> factors which should suffice for a fair portion, giving users a
> seamless experience.
>
> We will work on sharing this soon in greater detail.
>
> I apologize for not expanding enough on this since it does strike all
> of us as an immediate major risk to this plan.
Alright, i'm happy to wait and see.
I wanna note tho that right now it appears to me that anything below 99.865% CPAN dist coverage (i.e. the exceptions are a small, explicit, human-readable list with explanations that can be skimmed in under an hour) would be very dangerous.
Maybe i'm wrong, but i hope stating it like this gives you something solid to grapple with. :)
--
With regards,
Christian Walde
Thread Previous
|
Thread Next