On Wed, Sep 30, 2015 at 12:08 AM, Johannes Schlüter <johan...@schlueters.de> wrote: > 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.
Yep I also agree with that, we should reserve when we are sure (voted RFC) keywords will be used. Julien.P -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
