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.
