Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127040
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8DQqUhnb+U+WcA7bJ-APRDTtzuJC4m8s-q_2LH7bEuH+A@mail.gmail.com>
In-Reply-To: <CAMW7n8DQqUhnb+U+WcA7bJ-APRDTtzuJC4m8s-q_2LH7bEuH+A@mail.gmail.com>
Date: Fri, 4 Apr 2025 12:21:15 +0300
Message-ID: <CAMW7n8AnjLkkq=RrZe34xh9oWR6XUAEWHFLaj3g+oQVx7q2cdA@mail.gmail.com>
Subject: [PHP-DEV] Re: PHP True Async RFC - Stage 2
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001579c50631f06996"
From: edmond.ht@gmail.com (Edmond Dantes)

--0000000000001579c50631f06996
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Good day, everyone.

Just a ping email =E2=80=94 I haven=E2=80=99t disappeared, development is o=
ngoing.

Since the task has a high level of interdependency, I have to cautiously
try different combinations. The second-to-last version, in trying to
satisfy all requirements, turned out too complex to be taken seriously.

However, the previous version was brought to a logical conclusion, which
gave a clearer overall picture. Mind maps and feature-to-requirement
diagrams were very helpful, as they allowed me to view the RFC as a balance
between RFC complexity and code complexity.

I=E2=80=99ve finally managed to find a good balance, though this RFC still
surpasses all existing models in terms of tooling. I know minimalists won=
=E2=80=99t
like it, but this solution definitely deserves consideration.

Have a good day.

--0000000000001579c50631f06996
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p class=3D"gmail-">Good day, everyone.</p>
<p class=3D"gmail-">Just a ping email =E2=80=94 I haven=E2=80=99t disappear=
ed, development is ongoing.</p>
<p class=3D"gmail-">Since the task has a high level of interdependency, I h=
ave to cautiously try different combinations. The second-to-last version, i=
n trying to satisfy all requirements, turned out too complex to be taken se=
riously.</p>
<p class=3D"gmail-">However, the previous version was brought to a logical =
conclusion, which gave a clearer overall picture. Mind maps and feature-to-=
requirement diagrams were very helpful, as they allowed me to view the RFC =
as a balance between RFC complexity and code complexity.</p>
<p class=3D"gmail-">I=E2=80=99ve finally managed to find a good balance, th=
ough this RFC still surpasses all existing models in terms of tooling. I kn=
ow minimalists won=E2=80=99t like it, but this solution definitely deserves=
 consideration.</p><p class=3D"gmail-">Have a good day.</p></div>

--0000000000001579c50631f06996--