Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129923
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
 <CAMW7n8C1m08+pKKYBGkMnNZmGmu-_kkxS-r_SCuRupBY+RHe5A@mail.gmail.com>
 <CANCsWvfXWDjdmKFFQvV0Ger6yNVSfOhQqnbyTr7bEQHSjmXyLg@mail.gmail.com>
 <79CDB2CC-E397-436E-B5A2-10DA1E451A97@rwec.co.uk> <CAMW7n8BJcC-X-sA0NB_oQLfzry+331TfO1uhvNDGZcoSxe7bFQ@mail.gmail.com>
 <D427F18D-CDEC-4DDE-8169-71F8156F2E48@rwec.co.uk> <CAMW7n8BjxUUiizXbD1Lb526WsV=6erew-rK70gvMoWoQ2sqDmQ@mail.gmail.com>
 <CADK1yX+fA2epqOn2rcesmVBZMj4taeARhyuNdTky9aH4B6NhWg@mail.gmail.com>
 <CAMW7n8ALJ2w7iSwVX1TvyiosN_dzj=0NV0XBRZeQ3Hdov98C6Q@mail.gmail.com>
 <CAEKnhAFbU5H3qs-s0_FsT6w1Bu8n6HD+BQRt1SoOCUwa3XtT_w@mail.gmail.com>
 <CAMW7n8CFOafm21nbzPRx35ZXKzi-B0WC+7=X7dJMT=f=GDan-g@mail.gmail.com>
 <9f2fb78d-143e-c84a-8243-97e0352497e4@php.net> <CAMW7n8C41JB14qNM9SqjUEk3_nYMegMqUywR2if6g0YCLKFZ+g@mail.gmail.com>
 <9d2962b9-2278-4fae-9241-9def0f33711f@app.fastmail.com> <CAMW7n8C=87rrzxH4n=_XKkVhmxG731cdnsfF-ujYs1ko-O=j9w@mail.gmail.com>
 <213a47c7-cb2e-4d5c-b26b-ce18e3ce6d00@app.fastmail.com> <CAMW7n8BuzWbj18+1aVWzOvx-WOvN-Twa2TVh6VT+b16HE+szSQ@mail.gmail.com>
 <04bb674e-0a47-48d3-b19e-0cb9638cfc4f@app.fastmail.com>
In-Reply-To: <04bb674e-0a47-48d3-b19e-0cb9638cfc4f@app.fastmail.com>
Date: Sun, 25 Jan 2026 22:53:29 +0200
Message-ID: <CAMW7n8BDjVpLm-L+Hzzu_iUH9D1mHV59yLTL-F_HP6j2S0UP7w@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] True Async RFC 1.7
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

Hi

> I am going to attempt to take that time on this draft in the next few day=
s, but please don't pretend that it's not a large undertaking for those who=
 haven't been living and breathing this RFC for the past year.

I don=E2=80=99t want to pretend that this RFC is simple. I want to express =
a
different idea: by calling it =E2=80=9Cbig=E2=80=9D and =E2=80=9Ccomplex=E2=
=80=9D, it=E2=80=99s easy to fall
into the illusion that it=E2=80=99s impossible to analyze.
Especially since the number of pages does not reflect complexity. Some
parts matter more, some less. Some text is very important, while some
is almost irrelevant.

The amount of time needed to spend on this document depends on the
goal. If the goal is deep analysis, it=E2=80=99s more like a week or two. I=
f
the goal is to grasp the core idea, it=E2=80=99s more like 15 minutes to an
hour.

The required time will depend on the reader=E2=80=99s background. If someon=
e
is familiar with coroutines in Python or JavaScript, or has worked
with AMPHP or Swoole, this document should not be particularly
difficult for them.

I recommend looking at the PHP vs Python comparison documents right away:
https://github.com/true-async/php-true-async-rfc/blob/main/comparison-php-p=
ython.md

and for clarity, also at Go
https://github.com/true-async/php-true-async-rfc/blob/main/comparison-php-g=
o.md

+ Summary:
https://github.com/true-async/php-true-async-rfc/blob/main/comparison-summa=
ry.md

You don=E2=80=99t need to read all 55 pages here. If you understand this
document, you can almost skip the RFC.
It will be very difficult and painfully long only if someone is
encountering coroutines for the first time in their life.
But today, async has reached almost everywhere.

Ed