develooper Front page | perl.perl5.porters | Postings from November 2021

Re: Dogfooding our own new features - you can help

Thread Previous | Thread Next
From:
Dan Book
Date:
November 24, 2021 14:58
Subject:
Re: Dogfooding our own new features - you can help
Message ID:
CABMkAVXU25azAFeYk8RXgnqHji_jKhtuVh7c882hwNNcewTtFw@mail.gmail.com
On Wed, Nov 24, 2021 at 9:41 AM Paul "LeoNerd" Evans <leonerd@leonerd.org.uk>
wrote:

> On Wed, 24 Nov 2021 09:00:01 -0500
> Felipe Gasper <felipe@felipegasper.com> wrote:
>
> > Of these, only postfix-deref is officially production-ready, right?
> > The rest are experimental?
> >
> > I would think it better to avoid experimental features in core …
> > though once a given feature achieves official stability, of course,
> > it would be awesome to adopt it internally.
>
> "experimental" means "might change in a later version of perl", but
> that's fine for files shipped with perl itself. We can effectively
> ignore that status. If the feature does change then the file shipped
> with perl can just be changed to accommodate it.
>
> "experimental" means that someone somewhere has to experiment with it.
> If nobody does, then the status is effectively meaningless. Who better
> to experiment with it than ourselves?
>

I don't agree with this - experimental means (outside of exceptional cases)
it is unsuitable for production code because it may be insufficiently
shaken out or require breaking changes or get removed entirely. Core can
adjust in tandem with the feature for the latter issues, but not the first.
That doesn't seem suitable for code shipped with Perl which is not itself
experimental. At the very least, it should require case by case
determination on whether the particular feature is appropriate to use in
the particular module.

-Dan

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About