Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129429
Feedback-ID: id5114917:Fastmail
Date: Mon, 24 Nov 2025 11:54:38 +0000
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [VOTE] True Async RFC 1.6
User-Agent: K-9 Mail for Android
In-Reply-To: <CADK1yXJQNbk7p2AXkL3rsT4LizmGQFinuVESp37Ue7+nr8wX_Q@mail.gmail.com>
References: <CAMW7n8Dogjj2JFJBNArk-BfvOHRqHKMAFReXJAhDm2UPV1TF7A@mail.gmail.com>
 <1402906904.784903.1763811759896@email.ionos.de>
 <2015208655.784984.1763811978476@email.ionos.de>
 <CAMW7n8D0=6hEPpZpGe2SrYKqgFqsDkPAjHBP4g5K45bFPaiNdw@mail.gmail.com>
 <980296152.1071.1763813573083@email.ionos.de>
 <CAMW7n8DXA501uGOY3952y8YhAJDVRrPYEiuw+Wzc5=oEciLVZQ@mail.gmail.com>
 <92865666.4510.1763818506332@email.ionos.de>
 <CAMW7n8AycfX4NMfjJ+GzFsPqRaSae-t7Cm3H5z8apRzXUgaVZw@mail.gmail.com>
 <329450798.8037.1763822426377@email.ionos.de>
 <CAMW7n8DTt2S_RfcyshERixed=qqyFUPEvWp_MpgpW_CvH3urXQ@mail.gmail.com>
 <CAMW7n8CUQxqh4_rTWQBcj+t17i5oW7x-V96FSkwZL85Z2pzrRw@mail.gmail.com>
 <CAB9bCb34cmu9=an9K4rubPSVEDwyWH-rMAVtTTYa3U-LA+GJ+A@mail.gmail.com>
 <CAMW7n8DM4MCP25gSLBbd3+Awzs2+p6Qs_jPgx1mk=RjSVe+iUw@mail.gmail.com>
 <9287c46c-bc63-4dd0-9792-0f9421959589@rwec.co.uk>
 <CAJ6fn9N6z2sLr19RR_Zw65zT9mw1jf_cdJqtbZTcSu0=joOGaA@mail.gmail.com>
 <CADK1yXJQNbk7p2AXkL3rsT4LizmGQFinuVESp37Ue7+nr8wX_Q@mail.gmail.com>
Message-ID: <751A13E5-79AC-47C2-AFC7-A3B0AD69CA71@rwec.co.uk>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 24 November 2025 01:18:13 GMT, Deleu <deleugyn@gmail=2Ecom> wrote:

>If I could summarize months of discussion on this RFC, the primary topic
>would be the consensus that we do not want to have a split in the
>community=2E If every PHP package needs an adapter to be async compatible
>that essentially means the efforts to not break the community in half has
>failed=2E

Yes, this was precisely the point of my "SDK Susie" user story: Susie is n=
ot interested in maintaining multiple libraries for different parts of the =
community, she just wants her API to be usable by as many PHP developers as=
 possible=2E=20

If she can't use async I/O without breaking Legacy Les's application, she =
will simply not use it=2E Async Alice might write her own code for the API =
calls she needs, but won't want to maintain a fork of the entire library=2E=
 Beginner Bob will use the official library and not get any async benefits=
=2E=20

This is basically the situation we already have, with Async Alice using Sw=
oole or ReactPHP=2E



Rowan Tommins
[IMSoP]