Async Workers

[AlliBalliBaba]

There's been a new push to get native async into PHP, specifically via Fibers. While this is a good thing IMO, the Fibers approach probably wouldn't be compatible with executing PHP directly on go threads due how Fibers handle stacks.
If something like this really gets merged, it should be rather straight forward though to use go as a backend for some kind of async worker, similar to Swoole, but with threads. Is that also a direction you could see this project going into? Just curious to hear your thoughts.

[withinboredom]

I said as much on the list. I think it would be interesting to replace the scheduler with a frankenphp one. Judging from how the conversation is all over the place, I'd be surprised if it goes anywhere though.

[AlliBalliBaba]

Yeah I think that RFC tries to do too much at once. Would be nice though if this would at least result in a way to have native IO be non-blocking.

[withinboredom]

Yeah, though for 99% of php it won't make a difference. If you call file_get_contents, it still won't return until it has read the entire file. It's not like it will return a promise/future so you can do it in parallel. Thus you still have to write your code to do it in parallel if you want to do that, and with fibers, that is quite a bit of baggage.