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.
I/O is almost always the blocker.
Or would it be OK to recognize that most ecosystems adapt good ideas from each other?
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.
To only competitor I see is Rails. No other framework has such a rich and powerful ecosystem for web development.
Language features and non-web usage: basically everything
Handling concurrency/streaming: Phoenix
Simplicity while providing batteries: Flask
Backend/front-end integration: Blazor
I’ll definitely give you non-web usage and most of language features (even though PHP nowadays has first class type support, which can’t be said of Rails, unfortunately). And yes, concurrency is all but absent.
Apart from RoR, I haven’t used much else in the full stack framework space, so I’d love to hear!
Instead of Inertia, we have Livewire now Filament for amazingly quick and super powerful admin panels (like Avo for Rails)
Not including everything else available for auth, payments, basically any non unique SaaS feature has a good package available.
There is definitely concurrency with Swole (and implemented in Laravel with Optane, giving a 2x speed boost by default.)
This is just an example, not a strict advocation... I've been more fond of batteries not included options myself, and in particular been admiring rust options a lot.