PHP True Async
New RFC Strategy #33
Replies: 3 comments 3 replies
|
Hi Edmond, In the previous discussion, you mentioned that you were reaching out to the community, frameworks, and libraries for feedback. Have you received any feedback? What's the PHP Foundation's view on the best path forward? Are they interested in this feature? I noticed your internal email hasn't received a response yet. Have there been any behind the scenes discussions through other channels, or is this just stalled, hopefully because everyone is busy with the 8.6 release? |
I've only received a couple of responses, and none of them were from framework maintainers. That probably means the project isn't attracting much interest. Based on the ~32 emails I sent, that's the conclusion I can draw. Fewer than 5–8% of the recipients replied.
Yes, I'm in contact with two PHP core developers who support these changes. In fact, you could say it's even more their idea than mine. However, there haven't been any other discussions through any other channels. As for the PHP Foundation, I'm staying in touch with them. However, it's important to understand that the Foundation itself doesn't have the authority to make these decisions. That said, I think this is exactly the right time to establish an Async Working Group. There's another issue as well. It seems that, overall, the AMPHP team is more against the idea than in favor of it. The reason is fairly straightforward: they already have a large existing project and aren't eager to change it. As one of the developers put it:
|
|
We can only hope the state of PHP survey might show that the community that uses PHP daily is more interested🤞 I understand that the Foundation doesn't interfere with RFCs, but they do have paid developers, maybe they could use some paid time to respond to the internals mail with positive or negative feedback at least to start getting the decision going, if they feel the feature is worth it. That's a shame about AMPHP but understandable. I still hope to see async in the core ! |
|
Hope is important. But hope alone isn't enough. I also have a clear plan for what needs to be done. There's always a choice: |
|
https://discourse.thephp.foundation/t/php-dev-rfc-concurrency-support-in-the-php-engine/5817 |
|
I think, given the official's consistently dependent attitude, the probability of accepting the TrueAsync RFC is almost zero. I think it would be better if there were sponsorship teams. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
As you know, we're already into the second year, and the chances of the original TrueAsync RFC being accepted are close to zero.
The adoption of the Poll API opens up a new opportunity. There is now a chance to introduce changes into PHP core that would allow TrueAsync to exist as a separate extension, while also enabling other PHP extensions to integrate with the core much more effectively.
You can take a look at these two draft documents:
Both of these documents introduce hooks into the PHP core that can be overridden by an extension. They intentionally do not define a final, concrete design; instead, they establish the general principles and architecture.
The RFC is five to ten times smaller.
All reactions