Question: swoole and hyperf exist, what does this project aim to do about appserver HOT 1 OPEN

Hi, you're welcome to ask those questions, because they're comprehensible.

First, we've to say, that we actually do not have the necessary time to develop appserver.io up to the next level, e. g. a PHP 7.4 update or something like this. So sticking on PHP 5.6, it is outdated indeed.

As many of the documentation stuff around and about Swoole (and hyperf also seems to) seems to be written in Chinese language was and still are not able to read and understand it, although it will be cool stuff for sure. appserver.io kept the focus on writing everything that's possible in PHP and avoid using C which allows PHP developers to understand and extend it, starting from the HTTP Protocol and the webserver itself. Besides this approach, appserver.io comes with some - at least from our points of view - very useful services like a persistence container, a timer service and a message queue without the need to orchestrate a highly complex set of tools commonly used in PHP projects. So, as both will work, and for sure not appserver.io or Swoole will be the performance bottleneck in most cases, but the developer that writes the software, we think, the best solution for you and your project depends highly on how you want to develop software. If you like developing software in a node.js style, you'll be best settled with Swoole or hyperf, if you like developing software in Java style, you can go with appserver.io and will be fine :)

from appserver.