It's also not true. "Infinite are the arguments of sages," I hear, or something to that effect, but the distinguishing mark of expertise is not being able to offer an unqualified endorsement of any position.
The element of your comment that I find most concerning is that, after five years of using a programming language, I feel that you should be aware of its major flaws. Probably the minor flaws too. You should be aware of how it differs from other equivalent tools. And, if you don't know that, then the content of your post should not be "PHP is good," but "Why is PHP considered to be bad?"
Put that's not the point. It's not about bashing PHP for the sake of it. A large number of software projects is behind schedule and over budget. Why? Because developing software is hard and humans are bad at estimating effort.
Now why should we make the situation even worse by using tools that are not as good as possible while we are completely aware of the flaws (and good things) in our current tools?
Pointing out PHP's flaws over and over again while seeing that its usage does not drop tells us something - there seems to be no (obvious) better alternative. »PHP sucks!« is crying for help. Someone please build an obviously better alternative. Ideally as compatible as possible to make porting from PHP not practically infeasible.
What matters is that PHP has got big things right. Deployment is trivial. One process per request happens to mitigate leaks and (over)shared state. Failures affect one client at most, and scalability bottleneck is pushed down to the database.
The above has much less to do with PHP and more to do with the lack of experience of the developers, I would say..
"Tools as good as possible" is an extremely subjective thing, and there is no magical tool or framework that works perfectly in all hands.
Developers should choose the tools that are best suited to the job at hand, and "best suited" doesn't just mean the functionality and features, it also encompasses developer proficiency.