Customer Rating:  
Summary: A tough read for the newby
Comment: I was reading JavaScript by Example in parallel with Beginning JavaScript, 2nd Edition for a class. I found that Quigley was trying too hard to jam too much information into a small space. As someone new to JavaScript, I found her explanations difficult and her writing unclear. In comparison, Beginning JavaScript is bigger, but kinder and more comprehensible to the new reader. If weight is an issue, buy Quigley. Otherwise, you are better off with Beginning JavaScript.
Customer Rating:
Summary: Terrific book.
Comment: Terrific book, a little (editing) problems in the book, but if you have a little experience in Javascript they can be overlooked. Actually the few errors keep you on your toes!
Customer Rating:
Summary: Very good if you are the right type of reader for it
Comment: Wether or not this book is right for you, really depends on what you need from a Javascript text book. Armed with some basic knowledge of HTML, this was the perfect text to put me up to speed on the topic. There are many examples (as the title implies), giving you an exhaustive treatment of all topics. This treatment doesn't leave anything out, and though it would be nice to have the answers to the exercises, anything which stumps you can be solved by going over the examples again.
There are many explanations for every example given, but it's quite easy to skip around to what you need if you know some of the material already.
Excellent self-study tool.
Customer Rating:
Summary: Pretty good
Comment: A few discrepancies between the examples, explanations, and especially the CD, eg: where I think she changed a file or variable name in one place and forgot to change it in the other, so you spend some time trying to reconstruct what she meant to say.
Otherwise well paced, good for learning.
Customer Rating:
Summary: Inheritance
Comment: I think chapter 8 misuses the term "inheritance", which will muddy the waters for someone trying to understand inheritance. It says "Each object has a prototype whose properties it inherits". Would it be better to say "You can tack new methods or properties on to an existing class (eg: String) using the prototype property"?
|
|
