Può essere che tu abbia ragione. Comunque non sono l'unico a pensarla così, ecco una recensione su amazon

Anyone who gave this book a five star review didn't do anything more than gloss over it and rate the overall intentions of the author. As if learning how to program isn't hard enough, you're up against:

1. grammatical errors (which increase in frequency as the book progresses)
2. major code errors!
3. INFURIATING program inconsistencies (i.e. In ch5 you build a simple blog with the author. In ch6 the author wants you add functionality to the blog you built in ch5, but now he starts telling you to add to code that we never even wrote in the first place! He's telling you to change the previous code [which doesn't exist] to the new code, which you are hopefully resourceful enough to realize on your own by this point in the book... IT WON'T WORK WITH THE PROGRAM HE HAD YOU WRITE!)
4. Learning HTML on your own (there's not even a refresher in this book, you just have to know HTML or come back when you do)
5. Learning CSS on your own (no explanation at all on what this is... you just enter in the authors magic words and suddenly page looks right!)
6. Learning programming methodology on your own (search for Stanford University's youtube course on the subject and learned like crazy, then come back to this book and it will kind of make sense if you can translate the concepts on your own)
7. Learning all about .htaccess on your own (good luck beginners, much less absolute beginners, cause the explanation is nill)
8. Learning how the internet and web development actually works on your own.
9. Any error in your code and won't know if it's your fault or if you've simply been taught wrong... it's up to you to figure out who's gone wrong and where! SERIOUSLY

As it turns out, little did I know (nor did the cover or contents tell me), HTML is a pre-requisite. You should already be fluent in HTML. I'm sorry, but I wasn't quite an absolute beginner and I got my brain handed to me on a platter with this. The author introduces one concept, explaining it well, and then before you know it he's throwing another concept out there that you've never even heard before. You read on, hoping for an explanation that never comes. Solution = google + patience & suffering.

Somebody was in a BIG rush to get this book out. I have never seen such blatantly absent proofreading and editing.

That being said, I am learning PHP from this book. Perhaps the best teacher is the experience of not being able to trust the author's code. Hopefully people will figure this out on their own like I did instead of thinking their just not getting it! Giving up was not an option for me so I put the book down and went and learned HTML. I came back and learned a little more PHP and then found out that he wasn't going to teach me why he was doing what he was doing or what a ton of different words he was using were... so I went and took 8 hours of programming methodology at Stanford on YouTube! I came back and learned more PHP until I had to know what the heck he was doing with all this CSS, where I took a break and went to have a look at that. Then I came back and learned a tiny bit about databases from this book and then... well, you get the point. But if you have that level of perserverence, you can learn PHP like I did from this guy. Otherwise you will need to be familiar with programming already, not be a beginner!