* Vanilla PHP can't read anywhere near the same RPS as the others

* Using those results in removing the ability to use a large amount of the ecosystem. While if you used the correct language you would be able to use it's entire ecosystem.

* In my opinion, if you're using workerman or Swoole you've already realised the limitations of PHP and should be using another language.

This seems like a classic case of "if all you have is a hammer everything looks like nail"

> Might not be as fast as go, but to say these libraries or tech isn't production-ready is rather naive.

This strawman argument. Firstly, you admit my original point. Secondly, those aren't the tech in question and I notice you left off the tech in question. Roadrunner, FrankenPHP, etc. All the tooling that can make your average PHP app go faster.

Actually, there seems to be people arguing that.

> We’re arguing with you about your utter lack of expertise in the language, knowledge of the ecosystem and “production-ready” status of the many options, and your overall coding ability when it comes to PHP.

If you're doing that with benchmarks you're doing a shitty job. My numbers came from experience in production environments with production workloads.

Not to mention that you're talking experimental tooling as examples. I've literally seen multiple companies try to use FrankenPHP. Not one even made it to QA aka it broke because during the dev testing.