Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103806
MIME-Version: 1.0
References: <CAFPFaM+cEa2xFDqvkLQk=Qht3KdcGUCBaCj6JcuQxqLmjnf9Pw@mail.gmail.com>
 <d43d155f-9fd8-ddff-a44b-3dce2b2f6841@cubiclesoft.com> <CAG9XoMTK4j8R6_v++th2wRkdh5GZD4Vd9tKDt9YpXrhYmoH4uA@mail.gmail.com>
In-Reply-To: <CAG9XoMTK4j8R6_v++th2wRkdh5GZD4Vd9tKDt9YpXrhYmoH4uA@mail.gmail.com>
Date: Wed, 23 Jan 2019 17:36:51 +0100
Message-ID: <CAG9XoMRRO0mmfnuYrH5v4eFWOjRea-o0HmwezuWd=HXyOQT6WA@mail.gmail.com>
To: Thomas Hruska <thruska@cubiclesoft.com>
Cc: Girgias <george.banyard@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000029512f058022b452"
Subject: Re: [PHP-DEV] Deprecation ideas for PHP 8
From: benjamin.morel@gmail.com (Benjamin Morel)

--00000000000029512f058022b452
Content-Type: text/plain; charset="UTF-8"

> 2.78 million vs. 5.1 million* code references.
> 1.54 million results.
> 10 million results.  Broad, active usage.
> ...

I would not in any way base deprecation decisions on current usage
statistics. If there are several ways to do something, and one is clearly
better than the others (naming consistency) then the choice should IMHO be
imposed to the community.
Trying to make 10+ years old codebases work with recent versions of PHP
without modification slows down development a lot.
Major versions are here to break things. Changelogs and runtime deprecation
notices are here to help.

--00000000000029512f058022b452--