[echelon]

> It's always the same arguments, that $newHipLanguage will replace it.

It's not that a new language will replace it. It's that the people that hire PHP to solve their problem will now use a platform with no code to manage.

Engineers writing platforms will choose languages other than PHP to write them. You can't spin up multiple request threads to make concurrent non-blocking queries in PHP.

[ainiriand]

- You can't spin up multiple request threads to make concurrent non-blocking queries in PHP

You mean that you don't know how to: https://github.com/amphp/amp

[echelon]

It's not built into the language? How can we be sure this project with 2k Github stars won't segfault, memleak, deadlock, or have some other horrible bug [1]? I haven't done full due diligence, but I'm already suspicious. The open tickets don't look good [2].

> You mean that you don't know how to

I'm not convinced you found an appropriate answer either.

In any case, this should be a language feature.

[1] It looks like it relies on bindings to an unofficial native code extension.

[2] https://github.com/amphp/amp/issues/300

[ainiriand]

Don't look at js then.

[bufferoverflow]

> You can't spin up multiple request threads to make concurrent non-blocking queries in PHP.

I think you can.

https://dev.to/webong/using-asynchronous-processes-in-php-7i...