swoole-src

> I tend to install FOSS because imo they are more "future-proof", but some of them are developed by companies (e.g., Fedora Linux) and that makes me wonder if they're truly future-proof. The story of CentOS should be telling that, no, many pieces of software that are backed by a company will not be future-proof and will probably experience certain changes as a consequence of that, be it being transformed to better fit corporate goals (CentOS Stream), or being retired eventually so the company may focus on something else (Atom), or will just be left to slowly rot over time as happens with most code (OpenOffice). Then again, it's not like open source projects are that future proof or safe from "drama" either - for example, the Lubuntu project has 2 homepages for no reason: the official one at https://lubuntu.me/ and some other one that ser

> modern times to run php, people would use php-fpm with nginx, it is running multiple worker (single) process, so why would anyone [2], [3] wants multi-core coroutines in it? What does it even mean? Not everyone does. There's also https://reactphp.org (which is an event loop runtime, similar to Node), and https://amphp.org (also event loops), and Swoole https://github.com/swoole/swoole-src (coroutine runtime, similar to Go). Fibers are basically an API that event-loop runtime libs can use so that userland code doesn't need to use promises or generators to run non-blocking operations. Fibers are not useful for php-fpm or swoole users.

I would be a little bit careful while using swoole. They added some code that loaded code from a third party server [1] (a core developer who seems to be located in china). Even though it seems like they removed it doesn't bring a good feeling. It seems like there were also some disagreements with a contributor who maintained the website of swoole and he forked it [2]: https://github.com/openswoole/swoole-src [1] https://github.com/swoole/swoole-src/issues/4434 [2] https://news-web.php.net/php.pecl.dev/17446

Started with this shady commit of the owner that didn't mention anything about remotely downloading files: https://github.com/swoole/swoole-src/commit/73372ad07720f3f0...

More context here from the author of Swoole https://github.com/swoole/swoole-src/issues/4434

That is not a problem with PHP itself, but the way that Apache/Nginx operates PHP. However, if you want to go full PHP, there is this extension that is pretty amazing (has a built-in server on it and more): https://www.swoole.co.uk/ ps: https://github.com/swoole/swoole-src/issues/1401 some performances benchmark (they compare it even with golang)

For anyone interested in using channels and coroutines in PHP, swoole (https://github.com/swoole/swoole-src) provides a reasonable implementation!

I think the standard PHP model (one process per request), while still popular, is being replaced with fairly robust event loops. I've been using Swoole (https://github.com/swoole/swoole-src) in my company for about a year now, and it has matured into quite a stable code base, even if the documentation is lacking at times. The performance is pretty phenomenal and it has useful async coroutines for interacting with redis/MySQL/PgSQL. I saw some benchmarks in their GitHub issues list where it outperformed Node and Go (taken with a pinch of salt obviously). If you're afraid of something as experimental as Swoole, more stable options do exist, such as ReactPHP. Not quite as performant apparently, but seem to be popular. In general, I find that the PHP ecosystem is still thriving. It's definitely one of the easier languages to get up and runnin

On the topic of asynchronous PHP, swoole (https://github.com/swoole/swoole-src) is very interesting. Lacks documentation at the moment, but outperformed Node on a variety of tests I tried with MySQL.

Event-driven asynchronous & concurrent & coroutine networking engine with high performance for PHP. http://www.swoole.com/ https://github.com/swoole/swoole-src