Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113431
MIME-Version: 1.0
References: <D376DEFE-26A4-4F11-8548-D9454087E9FD@trowski.com>
 <8812EE70-4720-4639-926E-1EA206624BC1@trowski.com> <tencent_7FEAF879A5A1468B5C6FEE807780767DE705@qq.com>
In-Reply-To: <tencent_7FEAF879A5A1468B5C6FEE807780767DE705@qq.com>
Date: Wed, 10 Mar 2021 02:56:49 -0800
Message-ID: <CAPrKfG48iFS1QUV35gu2qCTt1bUOfZNs8n+fPyd1xWRqHHtniA@mail.gmail.com>
To: twosee <twose@qq.com>
Cc: Aaron Piotrowski <aaron@trowski.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c535e805bd2c8646"
Subject: Re: [PHP-DEV] [VOTE] Fibers
From: sarkedev@gmail.com (Peter Stalman)

--000000000000c535e805bd2c8646
Content-Type: text/plain; charset="UTF-8"

On Tue, Mar 9, 2021 at 6:03 PM twosee <twose@qq.com> wrote:

>
> 5. Not compatible with Swoole
>
> In my opinion, Swoole is an important part of the PHP ecosystem. But now,
> Fiber cannot work with Swoole. And based on the above reasons, Swoole will
> not consider compatible fiber.
>
> We would expect some ZendAPI rather than Fiber extensions to provide
> support for coroutine switching.
>
>
 Hi Twosee,

Are you saying that by adding this Fiber code to core it will prevent
Swoole from functioning? If so, that is concerning.  Or are you
simply saying that Swoole doesn't like this implementation and will not use
it with their own code?

One thing to consider when comparing the Fiber implementation is that the
vast majority of PHP applications are still run behind a web server in
short-lived requests.  Unlike Swoole, Swow, and Parallel, it isn't limited
to ZTS or CLI.  It might not be the ideal solution, but IMO it is a step in
the right direction for PHP to allow for better async support.

And I think you are right that "Fiber is just an enhancement of
Generator'', but so what?  The Generator addition in 5.5 opened up PHP to a
hacky way of doing async, but it worked everywhere.  Fiber allows that to
be much more convenient in switching contexts deep inside a call stack.  I
don't think it needs to be the end-all-be-all coroutine solution to rival
Goroutines, and I'm pretty sure it's not trying to be.

Thanks,
Peter

--000000000000c535e805bd2c8646--