> Then I got out of that job and again mostly forgot about it and curretly don't really care what happens to it.

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?

The more accurate statement would be: The only people who think PHP is dying is those who is not using it

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.

So, given you "don't care what happens to PHP", I assume you don't give much heed to whether it's winning or dying. That's basically what @deanclatworthy is saying, so there is nothing to fight about. Cheers!

Without giving a hint on the market share of PHP in the future, I think it tells something about its attraction force.

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.

I'm not fighting, I just gave a single data point that invalidated (logically, not actually) one part of his argument (the one I quoted) :) And then a bit of commentary.

The argument isn't that every person not using PHP thinks it is dying. As such, I don't see how your response invalidated it.

Also, the statement "that is absolutely not true" should probably be backed up by more than your single data point.