By the end of the book, assuming you haven't been stunned into a coma by the author's humor (yep, it's a US thang), you'll have a very superficial view of Java programming. What you won't have is the knowledge or the insight to produce anything useful.
This book, which has done well with new-to-Java novices, will occasionally receive a total ass-kicking at the hand of a professional coder like Pantziarka.
Without challenging his conclusion that my work sucks big rocks, I think that some coders misunderstand the target audience for a 24 Hours title.
My goal was to write a Java tutorial that could be tackled successfully by total beginners and people scared off the subject by the complexity of college courses and existing books. My imaginary target reader was a person who needed a moment to get his head around the concept of a multi-dimensional array.
You can't serve that audience without reducing to the language elements you believe are most crucial to understanding.
There are plenty of books that assume some level of comfort with basic programming concepts, but I didn't think that Java had a tutorial that could evoke an aspiring programmer's first "by George, I think I've got it!" experience.
I use this book to teach college students and they think it is TOO hard. Your book hit this market so well that it was originally the supplemental book and is now the primary textbook. I am a programmer with 25 years of experience but a professional instructor for 10 years and this book hits the mark. This isn't for a JAVA guru, but I am not teaching guru's!
When I set out to learn Java, I went out and bought two of those big "Learn Java Now" books, and "Java 2 in 24 Hours" was one of them.
I was working as a Perl programmer at the time, so wasn't down at the level to which you say you pitched the book, but it was still pretty useful to me.
Thanks. In writing the 24 Hours book, I had the advantage of also being the lead author on Java 2 in 21 Days. More of that book has been written for working programmers, so it covers in obsessive detail the kinds of things Pantziarka was looking for, like IO buffering.
I have found that the biggest challenge in writing these forest-levelers is to know when you've oversimplified something.