Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126656
Precedence: bulk
MIME-Version: 1.0
References: <9964db8c-0ffe-43d5-8246-47fc76b07180@app.fastmail.com>
 <CAMW7n8CM7oBfXCDsKtV4hTFs40UmLCU3183WjYE2exLNqKDWLQ@mail.gmail.com>
 <78a03dd0-fd4a-4f4a-ad8a-37e5704f06fc@app.fastmail.com> <CAMW7n8C-Z18MKhyDX2+ofg70cRbwWOk=YWDAZpKtfLZsFVVRng@mail.gmail.com>
 <bb7a9f8f-0422-45e5-b4fc-f5757add92b4@app.fastmail.com> <CAMW7n8BnzL7d0bd_Y_jGOmyWegKQpm-FzrVFRCcDe=bNFZpi+A@mail.gmail.com>
 <08c8ad0b-e8f4-46e3-99f0-b80748d40b89@app.fastmail.com> <07973EAE-2D83-47A8-8FA0-84286C77C02B@rwec.co.uk>
 <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com> <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk>
 <dbce8889-016a-4c59-864c-d8fdec895adc@app.fastmail.com> <CAM0Ccxh=bydoDEHBAV+Gb1_86HJjwhW06kzEsdRiMh93k1F7oA@mail.gmail.com>
 <8599eb8b-d4a3-4cb8-899a-25b134e0d64d@gmail.com> <D73BCCC4-3547-45B4-84AD-A5FD6569D43C@rwec.co.uk>
 <74c4c726-63aa-44e0-84c9-840e13a65a4f@gmail.com> <9b7ab30f-5ed6-400d-b941-1291e9185286@app.fastmail.com>
 <9a2e81e8-3534-455b-879a-5a45c85b3ba7@gmail.com> <de94a01a-ccee-423d-bd47-3e6257adfe7d@gmail.com>
In-Reply-To: <de94a01a-ccee-423d-bd47-3e6257adfe7d@gmail.com>
Date: Sat, 8 Mar 2025 20:37:37 +0200
Message-ID: <CAMW7n8D3Jv9w+em4=Vxqi__XB2KZcC0q7B2zKBxonuv7D=c1Rw@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
To: Daniil Gentili <daniil.gentili@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000003012b7062fd90969"
From: edmond.ht@gmail.com (Edmond Dantes)

--0000000000003012b7062fd90969
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
>  Crippling async PHP with async blocks just because some libraries aren't
ready for concurrency now, means crippling the future of async php.
>
How can calling a single function have such a destructive impact on the
future of PHP?

Yes, you have to write 10-20 more characters than usual one time.
Yes, it=E2=80=99s a hack. Every programming language with history has hacks=
.
Hacks evoke negative emotions. But life does too :)

All that=E2=80=99s needed is to change a few lines of code in index.php to
initialize the application in an asynchronous context. It=E2=80=99s the sam=
e as
launching Swoole: you need a few lines of code to initialize the web
server.

---

Ed

--0000000000003012b7062fd90969
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;<br>&gt;=C2=A0

Crippling async PHP with async blocks just because some libraries aren&#39;=
t ready for concurrency now, means crippling the future of async php.<br>&g=
t;<div>How can calling a single function have such a destructive impact on =
the future of PHP?=C2=A0=C2=A0</div><div>
<p>Yes, you have to write 10-20 more characters than usual one time.=C2=A0<=
br>
Yes, it=E2=80=99s a hack. Every programming language with history has hacks=
.=C2=A0<br>
Hacks evoke negative emotions. But life does too :)</p><p>All that=E2=80=99=
s needed is to change a few lines of code in <code>index.php</code> to init=
ialize the application in an asynchronous context. It=E2=80=99s the same as=
 launching Swoole: you need a few lines of code to initialize the web serve=
r.=C2=A0</p><p>---</p><p>Ed</p></div></div>

--0000000000003012b7062fd90969--