Swoole VS React

Swoole

It's a management UI where concerns were raised that it downloads from third party server. However this issue was handled very fast and code was removed: https://github.com/swoole/swoole-src/issues/4434

The contribution log of the original swoole seems to be active: https://github.com/swoole/swoole-src/graphs/contributors

FOMO is created by Iranian developer amirfaramarzi. This framework sits on top of the asynchronous event driven framework swoole that creates insane levels of performance out of apps (we're talking Go/Rust level of performance)! Check out the performance on the Web Frameworks Benchmark.

> 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 serves old versions and is not trusted by my ad blocking solution https://lubuntu.net/

There are also cases, when open source projects experience fragmentation like happened with Gogs https://gogs.io/ and Gitea https://gitea.io/en-us/ and sometimes there are cases where particular individuals simply cannot work together and as a consequence pretty much the same happens, as was the case with Swoole and Open Swoole: https://github.com/swoole/swoole-src/issues/4434

Treat most pieces of software that you use as if they might not be there in a year.

It's known by devs, it's simple, it's getting updates... I like PHP. Sure it has downsides but what doesn't. Oh, and with Swoole, even performance is bumped.

To allow for synchronous execution and prioritize speed, we decided to depart from the task-based system that most of our workers use and instead create a new component to Appwrite called the executor. The executor would handle all orchestration and execution responsibilities and remove the Docker socket from the functions worker. The executor is an HTTP Server built with Swoole and Utopia using various Appwrite libraries to interact with the database.

Swoole will be shipping something really-really cool that is it's own CLI. You can checkout the development at https://github.com/swoole/swoole-cli and you can start playing with it using the pre-compiled binary distributed under Swoole's releases at https://github.com/swoole/swoole-src/releases/tag/v4.8.7.

It's been around for more then 8 years. Its a very established project with more the 17k stars https://github.com/swoole/swoole-src

ReactPHP is a library that allows you to turn PHP into something like Go or Node.js so that tasks can be performed asynchronously. Note that ReactPHP is just a library that you install with Composer. It doesn’t have cumbersome requirements, such as installing a custom PHP extension; it just works as intended.

ReactPHP is categorized as a low-level dependency for event-driven programming. It features an event loop that supports low-level utilities, such as HTTP client/server, async DNS resolver, streams abstraction, and network client/servers.

So you could either skip the framework entirely and shave of these 10ms per request, or you could turn to something like Laravel Octane or ReactPHP to have a long running application that answers requests without bootstrapping the whole framework each time (which is what Node.js, Python or .NET applications do, the practice of restarting the whole app with every request is quite unique to the PHP community).

I remember calling out the movement to serverside of the frontend framework as reactPHP (I think it's when the remix hype first surfaced) on twitter and realized there's a literal php framework called reactPHP (https://reactphp.org/) since they liked my tweet lol.

https://reactphp.org/ of course.

You could also use something like EventMachine (In ruby), Twisted (Python), Node (JS) or ReactPHP (for PHP) that will use the language and turn it into a web application server, and then you'll have only one long running process that handle all your requests with shared memory. You could even use something more fancy like RoadRunner in the case of PHP.

Comparing PHP to NodeJS is completely wrong to begin with. If you want to compare NodeJS to something in the PHP ecosystem it would be ReactPHP.

Dunno about PHP core, but there is also ReactPHP. https://reactphp.org/

There are many micro-frameworks available like Slim, Mezzio(with Swoole may be), or if you are into async then you can also try Framework X(from core maintainer of ReactPHP). This frameworks have small footprints compare to Laravel, Symfony, etc. Yes, you can't get things like authentication, routing and other out of the box but they can easily be installed and configured to be used.