Re: async/await - is future reserved words in PHP 7.x?
| From: | Johannes Schlüter | Date: | Tue, 29 Sep 2015 22:08:02 +0000 |
| Subject: | Re: async/await - is future reserved words in PHP 7.x? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-88569@lists.php.net to get a copy of this message | ||
On Tue, 2015-09-29 at 21:04 +0300, S.A.N wrote:
>
> When Node.js appear async/await, many developers and projects will
> migrate to a Node.js, if PHP is not implement async APIs.
>
> Hopefully, Dmitry Stogov and others, will make another surprise:
> PHP-Next-Async? :)
My claim is that if you're doing something CPU-intensive which can be
parallelized in PHP you're most likely doing something wrong but you
should send this to a processing service. PHP imo needs a stronger
async-IO story.
Node.js is a completely different thing and people don't switch because
it has a async feature, but people pick it (aside from hype) since it
solves different issues.
Anyways. This is irrelevant for *this* thread. This thread was about
reserving async/await keywords. The discussion has proven that there is
no clear plan. Therefore we should not reserve any keywords.
If anybody has good research and a proposal they can start a new
discussion but let's finish this thread. If you disagree with my
assumptions feel free to answer *privately* but don't spam everybody
with off-topic comments :-)
Thanks,
johannes
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc