It does. Just look at quality of the documentation for starters.

Laravel is really excellent. PHP’s package manager, Composer, is great, and Laravel makes excellent use of it. The two main front end tools, Livewire and Inertia, are fun, with good starter kits. It has an elegant built in AI SDK, an official LLM developer integration, good payments support. There’s a new typescript binding. It has, IMO, one of the few truly well-designed ORM implementations.

There’s an incredible community around it. Lighthouse, the schema-first GraphQL package, is one of the neatest I have seen.

And PHP 8.x is a much more capable language than people expect. LLMs speak it well and are typically very up to date with its capabilities.

ETA: I think one of the things that sets it apart from other environments is the sense that it has a mature clarity of purpose, to be honest. In this AI-slop-documentation era, have a look at the documentation, the clarity of it, the ease of onboarding. Laravel as a project tends to execute well on ideas, has sensible defaults etc.; it just feels grown-up. It moves a little slower than other frameworks in terms of innovation, but sweats the details. It also has a well-managed upgrade process.

Unfortunately, I think PHP, and ultimately Ruby, Python, Perl, and Node.js, will all eventually be proven to be inappropriate for web development. It feels to me like we are heading away from a world where every application sits on top of an interpreter and a huge attack surface.

For myself, I really like Laravel; I have deployed apps in it that did good things for people and it was never once in my way. It has been fun, simple, even quite poetic to use. But I think I am done with these sorts of programming environments, and I am going to force myself back to things with a smaller footprint.

I certainly think that one aspect of PHP has to change, and that is the tendency to deploy with distro packages. That is clearly an inappropriate burden in the LLM-assisted hacking era.