Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119865
MIME-Version: 1.0
References: <aa9f0f66-f772-3fc4-4f66-2245930ab089@helionweb.de>
In-Reply-To: <aa9f0f66-f772-3fc4-4f66-2245930ab089@helionweb.de>
Date: Mon, 10 Apr 2023 23:17:36 +0700
Message-ID: <CAEZPtU6qV1OEBt7kaVoaxog=Wd4AZWNyiJW=1NMkASW8AJkRTA@mail.gmail.com>
To: Stephan Soller <stephan.soller@helionweb.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000414dde05f8fdb785"
Subject: Re: [PHP-DEV] Future stability of PHP?
From: pierre.php@gmail.com (Pierre Joye)

--000000000000414dde05f8fdb785
Content-Type: text/plain; charset="UTF-8"

hello,


On Sun, Apr 9, 2023, 1:37 AM Stephan Soller <stephan.soller@helionweb.de>
wrote:

> Hello,
>
> I'm sorry if this isn't the correct mailing list for that discussion but I
> couldn't find a more appropriate one where people actually know how the
> wind is
> blowing.
>
> A few days ago I migrated a project from PHP 7.1 to 8.2 and the amount of
> deprecations and fatal errors spooked me a bit (details below if you're
> interested). That got me wondering about the long-term stability of PHP
> (as in
> language and API breaks) and I looked at the RFCs. I got the impression
> that
> static typing has a lot of traction now and I have no idea of what the
> fallout
> might be of changing a dynamically typed language into a statically
> typed one.


I keep reading this in multiple languages, pr even more frameworks.

I understand agency work, managers pushing new features instead of a
cleaning some legacy.

however years of ignoring deprecation notices (very few were introduced
right before 8.0).

Most of them could have been fixed within a couple of hours in any code
base, if they had tests.

I would suggest, very very nicely, to review and rethink the development
flows of these projects instead of asking php to freeze.

best,
Pierre

--000000000000414dde05f8fdb785--