Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129275
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Sun, 16 Nov 2025 14:25:56 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <713f2209-912d-41d3-8c1a-5015a7fb2166@app.fastmail.com>
In-Reply-To: 
 <CAEUnE0fD0mqKv0PD+qbChmPj3btX4o-XyY9-qEJ_gW97EcX=Cw@mail.gmail.com>
References: 
 <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <CAMW7n8Dp3siTp0NKGc=-8aNg=Mqoxug9Osgn2399P1v4wi3n5Q@mail.gmail.com>
 <6618a91c-5393-4f40-88b5-b5041ee09deb@app.fastmail.com>
 <CAMW7n8CeDFSaN0e4Kr=1jrJyHEonHokfxcY4gdf6L3FqdH1FZQ@mail.gmail.com>
 <3e0cf0a1-c1a3-4e05-97ba-0eeb7f559a53@app.fastmail.com>
 <CAMW7n8AX7O7x99KGdPSai6sPP1Xd6V4ojQ7CEWmxthNLPM2hyQ@mail.gmail.com>
 <d17e07bf-9664-48e8-b7c4-39142f3cfbf2@app.fastmail.com>
 <CAMW7n8D3Mq6PveYxvfx=Djx6GnpkECOsEsEc2yKtJACAkAoLpQ@mail.gmail.com>
 <D0376B5C-7054-4948-BC48-5257F57B6129@zort.net>
 <CAEUnE0fcNP+R+r6rrMtUXcOYeCkutQzo-fTbkFpdL3VyLVXvQw@mail.gmail.com>
 <CADK1yXKS84aP9m=oExvL=rz2quGvXWKcPkV1h6gQj8vQUJjX3w@mail.gmail.com>
 <CAMW7n8ARHDQUeVKzsd44a11WGSuRm9CpvVK_D9YnBtMp9VxBSw@mail.gmail.com>
 <CADK1yXKsov2POUTrpzN+cKYk--H4kn6KmsMyUz_W7qfqEsCTQg@mail.gmail.com>
 <CAEUnE0fD0mqKv0PD+qbChmPj3btX4o-XyY9-qEJ_gW97EcX=Cw@mail.gmail.com>
Subject: Re: A Thank you (was Re: [PHP-DEV] PHP True Async RFC Stage 5)
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

On Sun, Nov 16, 2025, at 9:30 AM, Michael Morris wrote:

> It would be nice to have a coordinator process that does all this setup 
> work and stays alive handling requests by handing them off to workers. 
> That's how the various C# apps I've seen work. But that sort of setup 
> would require asynchronous code. So I can see a future use case for all 
> of this. But you don't need to convince me - I don't have a vote.

Alternatively, this is exactly what FrankenPHP solves.  Bootstrap once, run many times.  It doesn't require async to work, though it doesn't conflict with it either.  Personally I think FrankenPHP offers a more compelling way forward for taking PHP to the next level as it requires less retooling than async, but I am quite open to having both.

> Just, don't give up and don't get frustrated. It's hard. You can still 
> read the Drupal discussion on runtime assertions. I got rather testy at 
> times after explaining the same thing for the 12th time. But I didn't 
> take it personal and when my emotions needed checking I'd step away for 
> a few hours.

Oh dear, I remember those discussions. :-)  And yes, the biggest thing I learned from Drupal 8 is that *no one reads the <censored> plan*, and you have to explain it to everyone individually, personally, several times, even though you'd expect smart people to be able to *read the damned blog post that outlined the whole plan*, but they of course did not.

--Larry Garfield

PS: Please remember to bottom-post, not top post.