Swoole VS Symfony

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

Let's have a look at the class EventSourceHttpClient and try to use it in Symfony\Component\Webhook\Server\Transport. It's an entirely hypothetical example to illustrate the point.

Symfony is an open-source PHP framework developed by SensioLabs which has a thriving community of over 300,000 developers with 29k stars and 9.4k forks on GitHub. It provides a set of reusable PHP components and a development methodology for building complex and scalable web applications. It is recommended due to its advanced features and user-friendly environment. The user can also develop microservices.

Symfony 7

Would be great to see for https://github.com/symfony/symfony, thanks! As that's a monorepo it may provide a challenge to the tool.

As Shopware is mostly based on the Symfony framework, which is in turn based on the PHP language, we should also consider learning about the basics, which will also be useful for other frameworks apart from Shopware, like Symfonycasts, symfony.com, php.net.

Use PHP frameworks such as Symfony. It cares about all the stuff.

Symfony is a PHP framework. https://symfony.com/

It caused much of the internal of Drupal to be re-written. This included how it was extended. With previous major versions you learned about new features and APIs. They followed mostly existing design patterns so it was easy to learn and updates your extensions for. With Symfony you had to learn whole new systems and ways of doing things. It was like learning something entirely new. And, porting extensions to it was far more work and time.

Also, the updates made Drupal slower while consuming far more system resources for the same thing. This increased costs to operate.

Internally, the kernel executes a controller, that is a callable, passing it an array of arguments. For each of these arguments, Symfony calculates its value using services that implement the ValueResolverInterface1.

Drupal is one of the content management systems aka CMS. It has long history and good stability, which is based on PHP and Symfony.