[Legion]

"Modern PHP" basically boils down to "backporting features from the languages/ecosystems that have since replaced PHP".

Which is a great and smart way to improve PHP for the people who still have to work in PHP. But none of it is original to PHP, or provides a compelling reason to use PHP instead of the options where all these things originally were copied from.

[mgkimsal]

So should I use lang X for one feature, then shuttle that over to lang Y for another language feature, then marshall those results to a third language for its one original feature, then keep going?

Or would it be OK to recognize that most ecosystems adapt good ideas from each other?

[tracker1]

I think the point of GP is more that, if you're starting something new, you're probably better off with something that isn't PHP, despite the improvements that have been brought into PHP.

And yeah, many different ecosystems adopt ideas from one another. And it's often a good thing, though it can be hard for people with a lot of experience in something to see new syntax/ideas sometimes. It's also sometimes hard for people to invert/twist their thinking in different ways. I see this a lot when OO devs try to work with FP concepts. Another example is getting used to Rust's pattern matching and enum values.

[johnny22]

that's been php from the start when it was actually just a simpler way to build dynamic html.

[asddubs]

php is faster

[devmor]

Not that I agree with the person you're replying to, but while PHP is faster than almost everything else, that rarely actually matters in any application you'd be using PHP for.

I/O is almost always the blocker.