Interfaces, hmm. PHP took its whole OO almost directly from Java, which is an odd thing to do given how different the typing disciplines of Java and PHP are. Python's OO system is much more in-tune with the dynamic aspect of the language.
That is absolutely not true. I didn't care about PHP at all when I didn't use it. Then I got a job where I had to use it (and the management didn't want to hear about changing it), and I started slowly disliking it. Then I got out of that job and again mostly forgot about it and curretly don't really care what happens to it.
Weird defences like yours resurge the dislike, so there seems to be some amount of lingering trauma. And of course there's the worry that the more popular PHP is, the more probable it is that I will have to face it again some day.
Yet you made an account here today for this story to tell people how you don't care and why python is better than PHP.
Are you sure you don't care?
I had a similar experience as you. I used it for a couple of projects for a 1-2 years. When I realized PHP was an overpowered template engine, I started to think that it will be dying and moved on.
I mean, I didn't coded much Ruby over the last months in professional projects, but I am still interested with its evolution because it was such a delight to use it with Rails.
Regarding PHP, well, I did some in the past, and my next professional project include to deal with a PHP code base. In the meantime, I didn't care to use it or look at how it was evolving, which is "as exciting as your toothbrush" innovations.
Also, the statement "that is absolutely not true" should probably be backed up by more than your single data point.
The more popular a language gets, the more critics it receives. Partly happens because you will see more mistakes and bad quality code which also reveals bad design decisions in the language itself.
Some languages have more quirks, especially if they are older and tend to stay backward compatible.
Scala was known as a well-designed language (I believe still is) but as the community has grown, the number of complainers also has grown at the same speed. we learned people can write horrible code with implicit conversions.
But you need those critics to detect anti-patterns, and bad APIs and hopefully either the language itself or some libraries will fix it for everyone.
I code mostly in node nowadays, not through choice but due to the language snobbery I encountered during the last few years. It’s a shame. I find myself far more productive in the synchronous model than trying to bend my mind backwards with closures and async issues in the node world.