←back to thread

The Rise of Hybrid PHP: Blending PHP with Go and Rust

(yekdeveloper.com)
133 points avan1 | 2 comments | 30 Aug 25 19:02 UTC | HN request time: 0s | source
Show context
77pt77 ◴[31 Aug 25 01:32 UTC] No.45079541[source]▶
The fact that we're still pretending PHP is a valid solution for almost anything after all these years is a joke.

Not only that, but now we have these "frankenstein" solutions with all the interop problems on top of PHP.

Just shows that as a species humans really can't learn.

replies(2): >>45079703 #>>45081483 #
phendrenad2 ◴[31 Aug 25 02:08 UTC] No.45079703[source]▶
PHP really isn't that different from Ruby or Python these days. But, I can see the perspective where none of those 3 are valid solutions given newer better options like NodeJS and Rust.
replies(2): >>45079843 #>>45085946 #
const_cast ◴[31 Aug 25 18:57 UTC] No.45085946[source]▶
NodeJS is, like, 10 steps back from PHP 8. Worse type system, less safe, package ecosystem is a hot mess, slower... I mean the list goes on and on.

We can "lipstick pig" a lot of those problems by using typescript or whatever, but now we're compiling JS and the output isn't even fast. At that point use a competent compiled language like C# or Rust.

replies(1): >>45087166 #
77pt77 ◴[31 Aug 25 21:15 UTC] No.45087166[source]▶
As someone who is not a fan of npm/ts I must say I find this almost delusional.

TS is way better than PHP and node is much faster.

replies(1): >>45087950 #
const_cast ◴[31 Aug 25 23:17 UTC] No.45087950{3}[source]▶
TS type system is virtually identical to PHP - structurally typed, union types, etc. I don't know why people think PHP is untyped - it's not 5.4 anymore. The type system is very full featured.

The difference is TS has to be compiled, PHP doesn't. If we have to compile stuff we might as well use a more safe language like C#.

Also no, Node is not fast. I don't know why people think Node/JS is fast. JS has very poor performance characteristics and it can't be fixed because it's a factor of the language design - although, PHP has similar problems.

Chromium is very optimized, for specific scenarios. Its still a dynamically typed, garbage collected language - and optimizing a for loop in a play pretend medium blog doesn't change that.

replies(1): >>45088402 #
1. 77pt77 ◴[01 Sep 25 00:45 UTC] No.45088402{4}[source]▶
> Also no, Node is not fast. I don't know why people think Node/JS is fast

Node is not fast. It's faster than PHP and that is very clear.

The most cursory search and hands on experience will tell you that.

replies(1): >>45093133 #
2. const_cast ◴[01 Sep 25 14:54 UTC] No.45093133[source]▶
I don't think Node is faster than PHP because you can pretty aggressively optimize PHP. Between opcache cache, hot interpreters, JIT, frankenphp...

Chromium optimizes JS, sure, but not for that use case. It optimizes it for the frontend. I'm sure a huge part of that is how fast you can compile it - which means less aggressive optimize. I'm sure chromium absolutely does not optimize for long-lived JS processes.

Although, to be fair, I don't actually know which is faster. Just based off of my own experience, JS has been shockingly slow, and PHP quick in production. But that could be React clouding my view.

All in all, JS and PHP are pretty similar. The same stuff that makes JS slow is the stuff that makes PHP slow. Its not like JS has some magic sauce to turn an interpreted dynamically typed language into a performant one.