Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121291
Message-ID: <0b72d5e0-94dc-8837-bfd4-d2e24ab9db05@online-presence.ca>
Date: Thu, 12 Oct 2023 18:59:59 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.15.1
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Language: en-US
Organization: Online Presence
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [PHP-DEV] Why did fibers get added to php core over something more
 fleshed out like swoole?
From: lanre@online-presence.ca (Lanre Waju)

I find it puzzling that the PHP internals have chosen to delegate this 
specific functionality to userspace implementation. Fibers, in my view, 
seem somewhat limited without the addition of a third-party library or, 
at the very least, the necessity to implement an event loop in userland. 
This raises questions, as it effectively obliges users to rely on 
third-party libraries to handle a fundamental feature rather than 
incorporating it into the core of PHP.

Moreover, I'm curious about why PHPDBG doesn't implement the Language 
Server Protocol (LSP). Could it be due to its reliance on Xdebug? I came 
across this discussion on https://externals.io/message/78456, which 
makes me wonder about the decision-making process within PHP internals. 
It sometimes seems as though certain choices may not align with the best 
interests of the PHP community. I would appreciate it if you could 
provide insights into why this might not be the case.


Lanre