One of my biggest issues with PHP is that it doesn't cleanly separate the app and the system.
You configure your server to work with PHP, you set up access control rules on the server for what files they can see, you enable modules.
So then you need an extra tool to manage the configuration, and lots of YAML to declare what it should be.... meanwhile with Python you just plop it in a virtualenv and pip manages all the moving parts.
It's good to see the PHP ecosystem getting tools like this! Maybe we'll see more self hostable stuff we can install with one click now!
Its probably been a couple decades since I looked at PHP stuff (like php4 was probably the last version I used, though PHP5 might have just been released), but isn't that kind of how the main interpreter was implemented, and many of the patterns built into the language? IIRC there were things like default paths based on OS to system configs and stuff like that.
It never struck me as something that was designed to be ran as a user, but installed on a system and utilized by users. I'm just going by gut feels, but its my perception that other interpreters have more relative paths than PHP.
Other languages feel a bit more at home in a "Servers can be remade instantly from declarative config, manually making changes on a production server isn't a thing, and software is full of lots of third party pieces" environment, but then again, maybe I just don't use PHP enough to understand the idioms and ecosystem and there's solutions I don't know about.
You do? Can you be more specific about what tool you mean, and what YAML you need?