Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129242
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <CAMW7n8Dp3siTp0NKGc=-8aNg=Mqoxug9Osgn2399P1v4wi3n5Q@mail.gmail.com>
 <6618a91c-5393-4f40-88b5-b5041ee09deb@app.fastmail.com> <12D52EE4-62F4-42AC-A17D-A8F3A19D2433@zort.net>
 <CAMW7n8AuPXBqFMi=WCk=8=OR=SmWnfP1-=Ct1DbkcvfmFUt=2Q@mail.gmail.com> <c9250a28-30ff-4e4f-bf2e-914e4ae260d6@app.fastmail.com>
In-Reply-To: <c9250a28-30ff-4e4f-bf2e-914e4ae260d6@app.fastmail.com>
Date: Sat, 15 Nov 2025 23:24:41 +0200
Message-ID: <CAMW7n8A17NhNU2dK2B+VB+uETVGnenq+x5=CQ0K_uHd-F67wuA@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 5
To: Rob Landers <rob@bottled.codes>
Cc: John Bafford <jbafford@zort.net>, php internals <internals@lists.php.net>, 
	Jakub Zelenka <bukka@php.net>, Larry Garfield <larry@garfieldtech.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

> The examples you give here seem to contradict that. You are now saying th=
at developers must refactor shared state, must avoid passing objects to mul=
tiple coroutines,
> and must adopt a certain programming style to avoid breaking existing cod=
e. That=E2=80=99s the opposite of "works exactly the same without modificat=
ion".

I provided an explanation in my earlier messages.

> Right now, today, PHP has almost zero async code in the ecosystem.

That is not accurate. PHP already has a significant amount of
async-style code in the ecosystem: Amphp, ReactPHP, Swoole, Swow, and
multiple async HTTP clients, database drivers, and event-loop
libraries. The ecosystem is not =E2=80=9Calmost zero=E2=80=9D; it=E2=80=99s=
 simply fragmented
across several implementations.

> If the position of the RFC is that transparent asynchrony

My comment was about programming languages in general.