Re: PHP True Async RFC
| From: | Iliya Miroslavov Iliev | Date: | Sat, 08 Mar 2025 12:34:24 +0000 |
| Subject: | Re: PHP True Async RFC | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-126646@lists.php.net to get a copy of this message | ||
I will just put this picture here
On Sat, Mar 8, 2025 at 2:27 PM Edmond Dantes <edmond.ht@gmail.com> wrote:
> >
> > Colored functions completely preclude a possible future thread-based
> implementation of concurrency.
> >
>
> I can assure you that colored functions are neither part of this RFC nor *any
> future ones* from me. And it's not because it's my decision it's rather
> the language itself and the existing codebase that dictate the
> implementation. Moreover, we already have extensive experience with Swoole,
> where developers’ reactions are well known. And Swoole is essentially PHP +
> coroutines.
>
> I can recall the maintainer’s words from memory: it turned out that
> developers don’t want to use special functions instead of standard ones.
>
> I can confirm this from my own experience. For example, adapting a library
> for RabbitMQ required changing only 10-20 lines, and overall, it worked
> quickly without tests.
>
> The true strength of any language is not in its syntax. The main strength
> is its infrastructure.
> Even if a language is poor in terms of development quality, if it has a
> massive infrastructure, people will use it.
>
> ---
>
> Ed.
>
--
Iliya Miroslavov Iliev
i.miroslavov@gmail.com