Re: TrueAsync Engine API RFC
| From: | Rowan Tommins [IMSoP] | Date: | Fri, 01 Aug 2025 06:39:33 +0000 |
| Subject: | Re: TrueAsync Engine API RFC | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-128359@lists.php.net to get a copy of this message | ||
On 1 August 2025 03:20:58 BST, happyaa <happyaa@qq.com> wrote:
>Why is it so difficult to introduce asynchronous or coroutine features in PHP?
Because it's a complex feature, with a lot of scope to get something wrong and be stuck with an
unfortunate design for years to come.
>Has PHP been taken over by certain organizations or authoritarian individuals?
I refer you to Edmond's earlier update; far from being blocked, there has been positive
collaboration and forward planning <https://externals.io/message/127500#127502>
Please remember that PHP is written and maintained almost entirely by volunteers. There is no team
of highly paid engineers waiting to be told what project to work on, nor is there any central
planning committee dictating what anyone should work on.
There are a handful of people paid by the non-profit PHP Foundation so that they can spend more time
on the project. If you really want to encourage more work on complex features, a good way would be
to donate, and persuade businesses to donate, to that Foundation.
Or, of course, to volunteer your own time to tackle the challenges, even if that's just hanging
around here and giving *specific* feedback in design discussions, rather than vague assertions that
we're spending time on the "wrong" features.
Rowan Tommins
[IMSoP]