That is not exactly true, you can tweak composer to put dependencies anywhere you want them. What I feel is that there is a minor inconvenience, as many other languages have, and you try to build a case to bring down a whole ecosystem.
The difference is that in PHP, the developers of "Stuff\Mail" and "Tools\Mail" would have to define "Stuff" and "Tools" as the namespace for their code.
In Python, they don't have to do anything. The project that uses the code decides.
I can put those two mail modules in:
And then use them like this: I don't have to hope for anything.