Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119899
MIME-Version: 1.0
References: <aa9f0f66-f772-3fc4-4f66-2245930ab089@helionweb.de>
 <CAPyj-LAughwkC=nQjU=K56rMmCjPdmq42DPPr7Q0v0dtkieLzA@mail.gmail.com>
 <CADK1yXKWbwiUAmWpoOdCF459fzq3w47SpwBvJ_6-nXTnfzkjhQ@mail.gmail.com>
 <8abbed60-5569-4eca-ad12-957877feed9b@app.fastmail.com> <CADK1yXJj1=gfNLgUX69yED_pa5zJLJomyQ9M0K57zavu1fTikw@mail.gmail.com>
 <efa92c34-7296-44f0-b120-635a3590f8cb@app.fastmail.com> <CADK1yXKrxuBpScE7oWNo-dVPGi1p7wHCKRe28JhknBZxQy_B5g@mail.gmail.com>
In-Reply-To: <CADK1yXKrxuBpScE7oWNo-dVPGi1p7wHCKRe28JhknBZxQy_B5g@mail.gmail.com>
Reply-To: autaut03@gmail.com
Date: Tue, 11 Apr 2023 11:40:10 +0300
Message-ID: <CABigaAVZJgHSW5P735F=-NmjNQS=CVGtwRXbQS+HGG4_gfGP8g@mail.gmail.com>
To: Deleu <deleugyn@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000271d2205f90b7164"
Subject: Re: [PHP-DEV] Future stability of PHP?
From: autaut03@gmail.com (Alex Wells)

--000000000000271d2205f90b7164
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 11, 2023 at 6:10=E2=80=AFAM Deleu <deleugyn@gmail.com> wrote:

> I don't want to use those weird stuff, but I'm
> doing the best I can to replace every single line of old code that has be=
en
> written in an era that "best practices for PHP development" were not what
> you and I know today.
>

I still do not understand why you're expecting the whole PHP project to put
in enormous efforts to keep the backwards compatibility and solve your
problems (temporarily) instead of you doing so. What's stopping you from
using the last supported PHP version by that codebase and fixing or, worst
case scenario, rewriting it if you wish, while on that (non latest) PHP
version? What causes the desperation to update to the latest PHP? Is it new
features or security fixes, or both?

--000000000000271d2205f90b7164--