No such case is made in this book. In fact, a good chunk of this book is dedicated to building some project involving an SMS gateway instead of talking about the language semantics that make PHP what it is. The author's claim that he doesn't think there are any Bad Parts to PHP (in the "Bad Parts" appendix) shows he has not worked with many other programming langauges, if any, than PHP. I have a hard time believing the choice for the title of this book was meant for any reason other than to sucker people in (like myself) who loved Crockford's book and expected a similar "clean slating" for the other much loathed language of the web, PHP.
I was hoping for an in-depth discussion of the details of the language, the design choices its author made, and how to avoid common traps when writing PHP code. I wanted to see what functions and constructs to avoid, and what patterns were common enough to use idiomatically. Instead what I got was a basic introduction to the simplest concepts in the language ("Objects" being the epic crescendo of this grand tour) and many pages of rambling on about some SMS project. I would have read through it in more detail if it weren't for the author's ridiculously bad security through obscurity advice peppered throughout, which I'll spare him the pain of seeing reprinted here.
If you want to learn PHP, pick up another book. If you want someone to dissect the language for you and tell you how to write Good PHP instead of Bad, well, I guess we'll just have to wait for that book to be written. It's a shame someone has already taken the title it'll need.