Comment by that_guy_iain

Comment by that_guy_iain 7 days ago

What you're talking about is generally not considered production-ready. While you can use these tools you will almost certainly run into problems. I know this because as an active PHP developer for over a decade I'm very much paying attention to that field of PHP.

What we see here is a classic case of benchmarks saying one thing when the reality of production code says something else.

Also, I used go as a generic example of compiled languages. But what we see is production-grade Go languages outperforming non-production-ready experimental PHP tooling.

And if we go to look at all of them https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s...

We'll see that even the experimental PHP solution is 43 and being beat out by compiled languages.

Implicated 7 days ago

> ... you can have Go doing thousands of requests per second vs PHP doing hundreds of requests per second.

> I know this because as an active PHP developer for over a decade I'm very much paying attention to that field of PHP.

As an active PHP developer as well it sounds like you have no idea what you're talking about.

> While you can use these tools you will almost certainly run into problems.

Which tools are "generally not considered production-ready"? From what I'm seeing on the linked list of benchmarks...

- vanilla php - workerman - ubiquity - webman - swoole

I'd venture to bet all of these are battle tested and production ready - years ago now.

As someone who has built a handful of services that ingest data in high volume through long-running PHP processes... it's stupidly easy and bulletproof. Might not be as fast as go, but to say these libraries or tech isn't production-ready is rather naive.

Reply View 1 reply

that_guy_iain 4 days ago

Having read your post:
* 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.

Reply View | 0 replies

hipadev23 7 days ago

Nobody is suggesting PHP beats compiled. 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.

Reply View 2 replies

that_guy_iain 6 days ago

> Nobody is suggesting PHP beats compiled.
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.

Reply View | 1 reply
- hipadev23 6 days ago
  
  Again, you don't have the slightest clue what you're talking about. There are numerous production-ready choices that myself and others have mentioned.
  
  Reply View | 0 replies