On Fri, June 5, 2020 at 4:24 AM Nikita Popov <nikita....@gmail.com> wrote:

> On Fri, Jun 5, 2020 at 11:14 AM Nicolas Grekas <nicolas.grekas+...@gmail.com>
> wrote:
>
> >> It's that time of year again. Feature freeze is looming, so it's time to
> >> talk about deprecations!
> >>
> >> https://wiki.php.net/rfc/deprecations_php_8_0
> >
> > Thanks for the RFC.
> > Would it make sense for you to postpone this for 8.1?
> > I'm talking with my experience on Symfony here: we decided to give ppl
> > some rest when they upgrade and always have our *.0 versions
> > deprecations-free.
> > Chasing BC breaks is a hard enough task for ppl to upgrade. Adding the
> > additional step of solving deprecations is extra work that is not needed
> > yet. I know solving deprecations is optional, but many teams have CI that
> > fail on deprecations.
> >
> > I think it could be nicer to the userland community to have a smother path
> > here, IMHO.
> 
> Hey Nicolas,
> 
> I'm certainly open to that! I don't think there's any strong reason to
> deprecate any of these in PHP 8.0 in particular, as we'll only be able to
> drop them in PHP 9.0 anyway. Anyone else have thoughts on that?
> 
> We do already have a couple of deprecation in PHP 8.0, but those are
> generally directly related to some change that happened in PHP 8.0 in
> particular.

Because I follow the internals mailing list and RFCs closely, I don't
personally feel too strongly about which version the deprecations are
in, since regardless I can make sure my own code doesn't use these
features.

But for the large body of PHP devs that don't follow internals,
wouldn't they want to be notified sooner if something will be
deprecated? Waiting almost feels like keeping the planned deprecations
a secret from outside developers, resulting in more code being written
using these features in the meantime, and when they are finally
deprecated the migration ends up being more work than it otherwise
would be.

So while I understand the desire to make upgrades as easy as possible,
I'm not convinced it's a good idea to delay these deprecations for
a later release. At the very least if deprecation is likely the PHP
manual should say something about it.

Best regards,
Theodore
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to