I'm confused why the copy you generated repeatedly boasts "no nginx, no Redis" as if those things don't exist independently of application servers for a reason, and as if building something that doesn't need these things (when deployed as a single instance) is particularly notable.

"no Docker" - so what? Docker is a tool. Running containers on Linux has extremely low overhead. No idea what this is about.

You didn't spend the effort to decorate the slop with your rationale for these choices, so I see no evidence that you built any of this.

You don't need your database on a dedicated server. Not sure why the comparison table claims "$30 + DB server" when your web server is a perfectly good server already.

You can see the slop through the headline. No need to click. Posts like this are turning the internet into a trash pile. Nobody needs this slop, abandonware.

Heres the template:

"I" <--- prompted some LLM

"built" <--- to generate code for a

"fastest" <-- insert specious claim here

"PHP server" <-- thing

"And I prompted the LLM to build a website" <---- link

Im sorry folks but this just doesnt cut it anymore. I dont think it ever did.

I haven't used PHP as a daily workhorse in a decade, so I guess I don't understand why I would want a web server in pure PHP? Nginx exists.

I for one do not get the hate, nobody needs to use/or-waste-time-commenting on this project if they have no need/want. However, I do agree that it needs some more contributors on-board alongside with a couple months more support and bug squashing. And yes: better rewrite that website without the clanger involved in the wording! ;)

On a positive note: the performance is genuinely impressive.. what does it take to unlock this performance if I'm NOT running one of the big "usual" frameworks? The devil is always in the detail, best get some practical advice up on exactly what needs to happen with a medium piece of custom code to get it to said max performance.

for reference this is the interesting bit:

> run many workers. The server loads your entire framework into a parent process, then calls pcntl_fork() to create workers. The kernel marks the parent’s pages copy-on-write. Workers share every loaded class — they only pay for pages they actually write to during the request.

So its essentially preloading the memory layout. Cool idea.