Re: PHP True Async RFC Stage 5
| From: | Edmond Dantes | Date: | Sat, 15 Nov 2025 21:24:41 +0000 |
| Subject: | Re: PHP True Async RFC Stage 5 | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129242@lists.php.net to get a copy of this message | ||
> The examples you give here seem to contradict that. You are now saying that developers must
> refactor shared state, must avoid passing objects to multiple coroutines,
> and must adopt a certain programming style to avoid breaking existing code. That’s the
> opposite of "works exactly the same without modification".
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 “almost zero”; it’s simply fragmented
across several implementations.
> If the position of the RFC is that transparent asynchrony
My comment was about programming languages in general.