Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113494
MIME-Version: 1.0
References: <D376DEFE-26A4-4F11-8548-D9454087E9FD@trowski.com>
 <8812EE70-4720-4639-926E-1EA206624BC1@trowski.com> <tencent_7FEAF879A5A1468B5C6FEE807780767DE705@qq.com>
 <CA+kxMuSu=LS2BGjE0YYpOedVGq3dFXBSaqMdNtVkg0G2P73ywQ@mail.gmail.com> <tencent_0B3FA32A4F51EE36336DA75E@qq.com>
In-Reply-To: <tencent_0B3FA32A4F51EE36336DA75E@qq.com>
Date: Fri, 12 Mar 2021 14:14:54 +0000
Message-ID: <CAFPFaMLktkkPrUCwCfVxekCyfV1ia6v_yZ0vJBi--n28yJyyww@mail.gmail.com>
To: =?UTF-8?B?6Z+p5aSp5bOw?= <rango@swoole.com>
Cc: Dan Ackroyd <Danack@basereality.com>, twosee <twose@qq.com>, 
	Aaron Piotrowski <aaron@trowski.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d153a805bd57866c"
Subject: Re: [PHP-DEV] [VOTE] Fibers
From: george.banyard@gmail.com ("G. P. B.")

--000000000000d153a805bd57866c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 12 Mar 2021 at 04:06, =E9=9F=A9=E5=A4=A9=E5=B3=B0 <rango@swoole.com=
> wrote:

> Hi&nbsp;Dan,
>
>
> We have no commercial purpose on the swoole open source project.&nbsp;Thi=
s
> is a purely technical project.&nbsp;
> If possible, we can remove the name of swoole, contribute the source code
> of swoole-src to php-src, and transfer the copyright.
> Here is just a technical discussion.&nbsp;My opinion is that if PHP will
> support fiber/green-threads, this is a major change, should redesign
> language syntax, standard library, ZendVM.
> This proposal must be discussed extensively and in-depth,&nbsp;should not
> make a hasty decision.
>
>
> There are 7 parts to consider with my experience:
>
> EventLoop API
>
>
> Fiber/Coroutine/GreenThread
>
>
> IO-Scheduler (Socket/FileSystem/ChildProcess/Signal/Timer/Stdout/Stdin)
>
>
> CPU-Scheduler
>
>
> Compatible with existing extesions&nbsp;
> (php_streams/ext-sockets/ext-redis/ext-mysqli/ext-pdo-mysql/ext-curl ...)
> and builtin-functions (sleep/gethostbyname/proc_open/file_get_contents)
>
>
> Service container,&nbsp;How to support php-fpm and provide a coroutine
> version of http server
>
>
> Coroutine communication,&nbsp;How to pass messages between two coroutines
>
> It=E2=80=99s nice to see php has such topic. This may be the key technolo=
gy in the
> next generation of PHP.
>
>
>
> Thanks
>
>
> Tianfeng.Han
>

So from what I understand, and correct me if I'm wrong, you're against
Fibers because it doesn't include all the other systems needed to make them
immediately usable with the traditional APIs?
This sound a bit to me to wanting to run a marathon before even having
learned how to walk.

You said it yourself Swoole took *years* to implement all those changes,
and which is pure feature creep for what the RFC process is designed for
IMHO.
The point of this RFC, from what I see, is to bring the foundational system
into core upon which one can build upon, be that in userland or in the
extension land (when an internal API is added).
Upon which all of those different tools can be added to the language
independently, via separate RFCs, by being a PHP library or a PHP extension=
.

So can you please explain to us, why *not* adding one of the seven parts
you've stated are necessary and doing gradual implementations of the other
tools should not be done?

Because if the idea is to add all of these tools at once in a massive RFC,
I feel this is going the same way as trying to add unicode support to PHP,
and we know where that ended.

Best regards,

George P. Banyard

--000000000000d153a805bd57866c--