Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126644
Date: Sat, 8 Mar 2025 12:29:32 +0100 (GMT+01:00)
To: internals@lists.php.net
Message-ID: <52b37332-9330-4fe8-baf5-30b7a687da2a@gmail.com>
In-Reply-To: <db71834a-9ba7-47d3-8d06-0531eee9f0a0@gmail.com>
References: <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com> <9964db8c-0ffe-43d5-8246-47fc76b07180@app.fastmail.com> <CAMW7n8CM7oBfXCDsKtV4hTFs40UmLCU3183WjYE2exLNqKDWLQ@mail.gmail.com> <78a03dd0-fd4a-4f4a-ad8a-37e5704f06fc@app.fastmail.com> <CAMW7n8C-Z18MKhyDX2+ofg70cRbwWOk=YWDAZpKtfLZsFVVRng@mail.gmail.com> <bb7a9f8f-0422-45e5-b4fc-f5757add92b4@app.fastmail.com> <CAMW7n8BnzL7d0bd_Y_jGOmyWegKQpm-FzrVFRCcDe=bNFZpi+A@mail.gmail.com> <08c8ad0b-e8f4-46e3-99f0-b80748d40b89@app.fastmail.com> <07973EAE-2D83-47A8-8FA0-84286C77C02B@rwec.co.uk> <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com> <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk> <dbce8889-016a-4c59-864c-d8fdec895adc@app.fastmail.com> <CAM0Ccxh=bydoDEHBAV+Gb1_86HJjwhW06kzEsdRiMh93k1F7oA@mail.gmail.com> <05c426b4-4cea-46c3-9013-aa6cfb8b18b4@app.fastmail.com> <db71834a-9ba7-47d3-8d06-0531eee9f0a0@gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_27_243977606.1741433372334"
From: daniil.gentili@gmail.com (Daniil Gentili)

------=_Part_27_243977606.1741433372334
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


> Again, take a look at how nicely golang handles concurrency with colorless functions: php fibers weren't the first to do it.

Also, a colored functions approach for php would make a future thread-based concurrency approach completely non-viable, because it would require marking ALL functions (not just IO-bound functions, CPU-bound ones as well) as async and forcing the use of await for ALL function calls, just to be able to sometimes use some functions in parallel (in separate threads).

Colored functions completely preclude a possible future thread-based implementation of concurrency.

Regards,
Daniil Gentili.

------=_Part_27_243977606.1741433372334
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
 <head>
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 </head>
 <body>
  <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">&gt; Again, take a look at how nicely golang handles concurrency with colorless functions: php fibers weren't the first to do it.</span>
  <br>
  <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Also, a colored functions approach for php would make a future thread-based concurrency approach completely non-viable, because it would require marking ALL functions (not just IO-bound functions, CPU-bound ones as well) as async and forcing the use of await for ALL function calls, just to be able to sometimes use some functions in parallel (in separate threads).</span>
  <br>
  <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Colored functions completely preclude a possible future thread-based implementation of concurrency.</span>
  <br>
  <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Regards,</span>
  <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Daniil Gentili.</span>
  <br>
 </body>
</html>
------=_Part_27_243977606.1741433372334--