Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129284
Feedback-ID: i75064821:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Mon, 17 Nov 2025 10:08:05 -0700
To: internals@lists.php.net
Message-ID: <e1507f25-6f18-4a3e-add4-f144eea9b0db@app.fastmail.com>
In-Reply-To: 
 <CAEUnE0fcNP+R+r6rrMtUXcOYeCkutQzo-fTbkFpdL3VyLVXvQw@mail.gmail.com>
Subject: [PHP-DEV] Re: A Thank you (was Re:  PHP True Async RFC Stage 5)
Content-Type: multipart/alternative;
 boundary=e6936594ccae4780bea4dbc5cd856883
From: joseph+php@josephleedy.dev ("Joseph Leedy")
References: <CAEUnE0fcNP+R+r6rrMtUXcOYeCkutQzo-fTbkFpdL3VyLVXvQw@mail.gmail.com>

--e6936594ccae4780bea4dbc5cd856883
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Sun, 16 Nov 2025 00:12:56 +0000, Michael Morris wrote:
> I've been reading this discussion from the peanut gallery. I don't have
> enough knowledge to really add anything to the conversation, but I do want
> to take a moment to thank everyone involved. Of the changes to PHP since 7,
> this promises to be some of the most significant. The care and time taken
> to get this right is greatly appreciated. To all participants of the
> thread, thank you.

I too would like to join the thank you train. I appreciate the time, thought and detail that you've put into this proposal, Ed. I myself don't quite understand async and I've struggled to work with it in JavaScript (looking at you, `fetch` and `Promise`). That said, I'm glad you added the summary to the RFC, which breaks down your goals into easy to understand pieces.

A huge thank you to all of the participants in this discussion as well as the reviewers. I know that not everyone agrees on what the final implementation will look like, but I hope that you all can find a common ground and move forward with this monumental new feature. (Ideally something close to what has been proposed by the RFC in its entirety.)

Best Regards,
Joseph "Seph" Leedy
--e6936594ccae4780bea4dbc5cd856883
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>On Sun, 16 N=
ov 2025 00:12:56 +0000, Michael Morris wrote:</div><div>&gt; I've been r=
eading this discussion from the peanut gallery. I don't have</div><div>&=
gt; enough knowledge to really add anything to the conversation, but I d=
o want</div><div>&gt; to take a moment to thank everyone involved. Of th=
e changes to PHP since 7,</div><div>&gt; this promises to be some of the=
 most significant. The care and time taken</div><div>&gt; to get this ri=
ght is greatly appreciated. To all participants of the</div><div>&gt; th=
read, thank you.</div><div><br></div><div>I too would like to join the t=
hank you train. I appreciate the time, thought and detail that you've pu=
t into this proposal, Ed. I myself don't quite understand async and I've=
 struggled to work with it in JavaScript (looking at you, `fetch` and `P=
romise`). That said, I'm glad you added the summary to the RFC, which br=
eaks down your goals into easy to understand pieces.</div><div><br></div=
><div>A huge thank you to all of the participants in this discussion as =
well as the reviewers. I know that not everyone agrees on what the final=
 implementation will look like, but I hope that you all can find a commo=
n ground and move forward with this monumental new feature. (Ideally som=
ething close to what has been proposed by the RFC in its entirety.)</div=
><div><br></div><div>Best Regards,</div><div>Joseph "Seph" Leedy</div></=
body></html>
--e6936594ccae4780bea4dbc5cd856883--