9 comments

[ 4.3 ms ] story [ 29.1 ms ] thread
It even has a template engine! Because the one thing PHP really needs is a good template engine.
How do you honestly benchmark a framework that only has a documentation of a hello world against laravel which has about everything you can think of...
Stuff like this gives me so much FUD. It's cool, but a simple memory management bug means your boring PHP app can have any number of terrible problems: memory leaks, RCE, corruption, you name it. At least with popular, mature C-based software with lots of eyes on it, you can feel a little bit confident that issues have been sussed out. But something like this with probably a small number of production users? Scary!
> One major drawback for PHP is that on every request, all files are read from the hard drive, translated into bytecode, and then executed.

How old this this framework? Sounds like they never got the news that opcache has been part of PHP since 2013.

Seems like a tone-deaf name for a new project in 2026...
This is very far from a new project. The first commit and issues are from 2014.
Strong CodeIgniter vibes in how the API is presented, which I'm not a fan of.

Unclear how the benchmark was setup but with php-fpm and opcache preload many hundreds of requests per second is my experience with Symfony.

Good news, guys! The maintainer updated the repo fifteen months ago so that the copyright in the license file mentions "2025".