Hi Benjamin, On Fri, Feb 15, 2019, 2:26 PM Benjamin Eberlei <kont...@beberlei.de wrote:
> > Async.io is used for scalability In languages with entirely different > architectures than PHP. > > Node.js isn't well suited to monolithic applications such as Wordpress, > Magento and the fast amount of applicatoins that people are building in PHP > right now. > One needs some supporting microservices here and there (to do websockets, > high throughput work with lots of I/O, small daemons, ...) which right now > people are using Go or Node.js for next to PHP, swoole or react-php. > This is like the 80% use-case of threading, Multiple HTTP requests, > multiple long running SQL queries. An API like parallel would allow > each and everyone of us to make controllers faster today without a > large effort. > > Swoole is nice, but it will never be the 80% use-case for PHP users. All async I/O APIs heavily lean on node.js APIs, which is an entirely > different paradigm to program on and not PHP. Plus you have to rewrite > all libraries to support this, instead of being able to re-use the > libraries and style that PHP has championed for all this time. > I think you are right in your analysis. However I fail to see where you are heading to. It is the same as when couchbase or other Mongodb drivers were created, or OO features. 100% of the existing code base were not suited for them. Still, these features open new doors for php as a leading web language. The same applies to async io and to some extend parallelism (in different area than web servers tho'). And yes, async requires much more efforts (overall applications architecture) to port libraries or application to fully use them and benefit from async IO. I am convinced PHP will be able to have these features and remain a leader for a few more years. PS: I will still use node, go or Python as well as always ;-) best, Pierre >
