A question on the future of this library

[Vectorial1024]

Hi there, it turns out I have totally forgotten that I have been here before, because some time ago I have decided to abandon this concept due to lack of community interest.

I still believe we are/were onto something, but we just can't seem to get it right or get the word out.

Still, recently there was a PHP True Async RFC that promised to add concurrency to PHP, which is basically what we both are/were trying to do. It seems this time the RFC is getting some positive responses.

Would the RFC be enough to replace this library (and also my other similar library), or are there something more planned for this?

[terremoth]

Would the RFC be enough to replace this library (and also my other similar library), or are there something more planned for this?

Hello there!

No, It won't be able to replace yet, because this:

they are focusing on CONCURRENCY, not parallelism. So even if they release the Async API, it will not be "in parallel", something that is achieved (but not controlled - yet) by this library in a easy way.

The fact is that: PHP by itself is kind of thread-blocking. To transform php in a non-blocking programming language (or with sufficient resources to do so), it would need to refactor a lot of the core language, a thing that won't be achieved easily nor nowadays.