Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88569
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
Message-ID: <1443564482.10840.7.camel@kuechenschabe>
To: "S.A.N" <ua.san.alex@gmail.com>
Cc: Aaron Piotrowski <aaron@icicle.io>, Thomas Hruska
 <thruska@cubiclesoft.com>,  Joe Watkins <pthreads@pthreads.org>, Kalle
 Sommer Nielsen <kalle@php.net>, Pierre Joye <pierre.php@gmail.com>, Levi
 Morrison <levim@php.net>, PHP internals <internals@lists.php.net>
Date: Wed, 30 Sep 2015 00:08:02 +0200
In-Reply-To: <CALW=WECiCWgY_JzJB_8jxm2_oqT4MD72gLWUaZmKe6MMQxoVxQ@mail.gmail.com>
References: 
	<CALW=WEBPC2N2tzmU1uB_v93YXLa1MA97=0_q7zP0F6G+uRPDNQ@mail.gmail.com>
	 <56095A0C.4070306@cubiclesoft.com>
	 <CAFMT4NqaqVX-KHh9iz_R05wxp2h=aajv5RuQGh2EQVSNHoLGaQ@mail.gmail.com>
	 <CAEZPtU6cgVrqh0PNYybcrk4_X36m5K=dp280G=7OfzjYBzxJpQ@mail.gmail.com>
	 <CAJW__o2727mc+ugUd2NvvYTB-r0dC68dkUOke+oPjwZDtZA+vQ@mail.gmail.com>
	 <1443529244.15520.67.camel@kuechenschabe>
	 <CAL=_i_kXeBiQ4O9u-0mXu47zKt2-c9uQSWGZ4KReTfjzbzT7kw@mail.gmail.com>
	 <560AACB6.9080909@cubiclesoft.com>
	 <09A2B2D4-EAE9-46E8-AF5C-4E83C4F3D8A2@icicle.io>
	 <CALW=WECiCWgY_JzJB_8jxm2_oqT4MD72gLWUaZmKe6MMQxoVxQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-i0B2mT5OeRkGZN6jGQDP"
Mime-Version: 1.0
Subject: Re: [PHP-DEV] async/await - is future reserved words in PHP 7.x?
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

--=-i0B2mT5OeRkGZN6jGQDP
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 2015-09-29 at 21:04 +0300, S.A.N wrote:
>=20
> When Node.js appear async/await, many developers and projects will
> migrate to a Node.js, if PHP is not implement async APIs.
>=20
> 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


--=-i0B2mT5OeRkGZN6jGQDP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAABAgAGBQJWCwvCAAoJEH3sTmn8nIPXemUIAMpseJ8CMk6WUNq5HqlnT4KS
GxOH0r+f8HTPx8j1efy4OYbRFtNg32fTGVjI23sGfsa4h6AktoQJDylQzi0pQcbx
I7WaCQ5xHVrzxHbxkdgjey12J6shxrcE7JRJnQ9FqwdYw8FJw5eoQlP3rLbu9VBI
XkWj+aWS45R2fOBKL68+SElpcOTZd/aYo7yReXYSzl+OrRjJF0Q6Xb8rFsdhvwRX
zqr7iV0UBq/2BTi6+lMzStF6KCI+oT5oMIypE+ptnTAmvU5UoVSwmiAW5UjJC8lP
QZRrrr3nzn7T9JM1+fKNNBfukTPqzp/yduS12Nc7Qxj/hSm+p57/ystoFP9MkFU=
=qCak
-----END PGP SIGNATURE-----

--=-i0B2mT5OeRkGZN6jGQDP--