termwind VS RoadRunner

The app is based on Laravel Zero by u/nunomaduro, and it uses Termwind to render the release notes to console with styling and clickable links.

Introducing a fresh new look for Artisan https://github.com/laravel/framework/pull/43065 https://github.com/nunomaduro/termwind

Concerning styling, if you need to push the appearance of your console program a bit further, you might want to take a look at Termwind, a promising new framework described as "Tailwind CSS, but for PHP command-line applications".

This project really comes out of need after years of trying to make CLI applications look unique — styling-wise. Now, it’s easier to build unique, custom CLI designs without fighting with the console. We hope you are as excited about Termwind as we are. ✓ github.com/nunomaduro/termwind.

Since this post got most of the traction while your previous did not, I do want to ask the same question again: how does this compare to Termwind ? A package that started a few weeks before yours if I'm not mistaken?

FrankenPHP

why link to the old URL when linking to its redirected one is less confusing?

https://github.com/roadrunner-server/roadrunner#readme (MIT)

Don't follow any advice to use Apache as a reverse proxy, or bundle php with a classic web server.

There are real application servers using an event loop by now, most notably Roadrunner (https://roadrunner.dev), FrankenPHP (https://frankenphp.dev), Laravel Octane (https://laravel.com/docs/10.x/octane#introduction), Swoole Bridge for Symfony (https://github.com/insidestyles/swoole-bridge-bundle).

In general, you can do a lot with OpenSwoole or Roadrunner. They are vastly superior (in a container scenario) to any other suggestion in this thread!

https://roadrunner.dev which golang php application server which can replace nginx +php fpm has a module for running golang via php using sockets.

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.

Have you considered optimizing the Laravel app? I love Go, but full rewrite for such low rate sounds overkill. Have you looked at the RoadRunner PHP application sample, for example?

Has state resetter for long-running workers serving multiple requests such as RoadRunner or Swoole.