Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129040
Message-ID: <ccb69ad4-5875-4bf4-92c7-50d1bd677ff2@dennis.birkholz.biz>
Date: Sat, 1 Nov 2025 14:15:09 +0100
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 5
To: internals@lists.php.net
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <2441aa9c-41c8-4ce1-b9c0-67136e5f97da@dennis.birkholz.biz>
 <CAMW7n8A6A-61Q1dzvQxhud0WYQdOKdANqmRbgNg2o=-Qyg5snA@mail.gmail.com>
Content-Language: de-DE, en-US
In-Reply-To: <CAMW7n8A6A-61Q1dzvQxhud0WYQdOKdANqmRbgNg2o=-Qyg5snA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: php@dennis.birkholz.biz (Dennis Birkholz)

Hi Edmond,

thank you for your reply.

Am 01.11.25 um 8:32 AM schrieb Edmond Dantes:
> A Fiber in PHP is a context that stores a pointer to the C stack, CPU
> registers, and part of the VM state, combined with a generator.
> Fibers cannot be used as coroutines because this approach is
> inefficient in terms of performance and memory.
> The reason is that a Fiber is an extremely low-level primitive — only
> slightly higher than assembly.
>
> Therefore, Fibers violate the **Strict Layering** principle ...

 From the standpoint of PHP language user, I have a completely different 
view on Fibers vs. Corotines.
They look very similar from the outside and if we talk about 
abstractions, that is the point that matters as the inner workings are 
hidden.

I really belief we should avoid fragmentation and enhance/adjust Fibers 
to meet the memory and performance requirements of a Coroutine.

Thanks
Dennis