This is by far the most horrid book! The tutorials and case studies have nothing to do with each other! You really cannot learn anything from this book at all. The organization of this book is bad period. Not for beginners at all. I will have to drop my javascript class because I'm learning nothing! Do yourself a favor and buy the teachers edition!

Similar to other reviews my entire JavaScript class is two weeks behind trying to get a understanding of this material. The tutorials are great! But the case studies personally make me want to stick a fork in my eye and twist it. The way its worded, they want you to grab code out of thin air expecting you to understand everything in that overly simplified review/tutorial.

I think teachers like this book because they are NOT looking at it from the view of the students and already know the code; or they wouldn't be teaching it. Of course they think its a great book they already understand the material.

The book does not get any better as the chapters go on. I cant even complete the case studies; the teacher has to walk us through every class period with little time left over for lab work.... My advice to teachers, do a bit more hands on training and DO NOT rely on a book; Especially this one.

Myself and 10 other students in my Javascript class all agree and have announced to the instructor that this book is horrible. Also, 3 people just dropped the class because no one is understanding or learning anything. This is our first javascript class and this book is no where near intro or basic. It says it's comprehensive.

Not only that, but the tutorials they try to show you throughout the book have nothing to do with the case assignments after each tutorial. You basically have to do your own internet research to get the code, but that still is a little difficult.

Perhaps due to the presence of coauthor Frank Canovatchel, there is slightly more clarity of thought and rigor applied to program logic presentation than in the other Carey book I reviewed (XML).

However, I have to agree that the Review exercises at the end of each tutorial (I'm at Chap 04) tend to leave out critical information that doing the chapter tutorial should have taught. It doesn't.

And to make matters worse, the index is incomplete. A pet peeve of mine is text books where you can't find information you either thought you read [and want to review] or want to know if it is somewhere in the book you plan to read [but haven't read yet].

Case in point: Review exercise of Tutorial 4, Step 5 says "Use the getObject() function to create three variables..." but the closest thing to a "getObject()" function mentioned in the chapter (or the book as far as I can tell) is the getElementById() which does not appear to be what is intended in this exercise. To make matters worse, the index does not list a getObject() function. Googling online revealed numerous tangentially related topics, mostly appearing to do with Microsoft and VB. So....one simple missing step and the exercise is dead in the water. Very typical of Thomson Course Technology textbooks I might add.

So two stars because the chapter tutorials proper can usually be copied line for line (legal transcriptionist style) and will often work (not always, for example Chapter 03 tutorial created a opening HTML table tag and never ended it. Makes me wonder how well the code was tested.). No more stars because the end of chapter exercises are only moderately clear and tend to require that you somehow intuit exactly what logic the author had in mind at the time he was writing, and book is nearly useless as a reference to find more data. It is not for loss of words. The author writes like he is paid by the word. The exact same code is repeated three times in consecutive order but slightly different text formatting (for reasons known only to the author or publisher) and the verbosity of writing style would make a politician green with envy - yet seldom does it clearly and categorically really 'say' anything. Definitely not K & R.

Lastly, the text mentions color in several places. For example, p. 172 states "In the figure, object names are highlighted in red, methods are displayed in blue, and parameter values are diplayed in green". I need not state the obvious: The book is printed in black and white. Obviously, a printing decision was made after the text was written and nobody bothered to proof for mention of color. Not to mention the resulting loss of information.

I only bought this book because it was required for a class - I previously had the displeasure of another Carey/Thomson Course Technology book [XML] and know better than to buy one voluntarily.

[btw, It doesn't help that IE7 javascript debugger gives clues about as illuminating as tea leaves. "Expected object, line 54, 1" - which is perfectly good, only said object is a container for all the code written in the exercise....well now that really narrows things down!!! :-( ]

If you're looking to get into JavaScript for the first time, this book is probably for you. If you're trying to create commercial sites or become a JS pro, probably not. It's good for classes where students can follow the tutorials.

This book says Copyright 2006, and looks like it was released in late 2005. However, judging by the discussions on browsers and the lack of any mention of the latest uses of Javascript (Web 2.0, Ajax, etc) this book seems more like it was written in 2003. It mentions version 4 browsers all over the book. Makes no mention of Firefox or Safari, and does not discuss versions of IE and Netscape that were out even in 2005.


The Chapters, called Tutorials, are overall pretty good at explaining the topics. However, there are at times where they aren't really explaining "why" you're doing something, just showing you how to do it. This approach is not very educational.

Another complaint was in the wasted half chapter on using "filters" that only work in IE. I'm taking a class that is using the book. After going over these topics, the instructor took a vote on how many (out of 30 people) found these IE only parts helpful...about 3 people thought so. Most people, me included, felt it was a waste of time. Most of the IE filters can be done with other technologies that are cross-browser compatible, making it pretty bad practice to use them at all. So, here, the author just wasted space - and class time.

I can't compare this to any other Javascript books, but I can compare it to there computer books. It's just OK. I'm sure there are better books out there that cover more timely topics, include discussions of the latest browsers (even for 2005!), don't waste time on teaching proprietary technologies (IE filters), and cover topics that explains more of the "whys" rather that just "hows".

This text is written in a very odd way for beginning students. The chapters, called "tutorials", walk you through the process of coding javascript by telling you how to do this or that in a series of handholding steps that seem decent for beginners. It is a natural assumption that once a person has finished a tutorial, they should be able to tackle the case studies at the end of the tutorial with minimal problems. This assumption would be very wrong. The case studies were not meant for the beginners like the tutoprials were. They are far too complicated, assuming that the average student has just become fluent in javascript after the over-simplified, step-by-step tutorial. As Mark Mattix states in his review, be VERY prepared to need other sources to help explain the concepts the case studies in this text were designed for.

The tutorials in the book are written well, but the exercises are just too confusing! They want you to take everything from previous chapters and incorporate it to write new code. They expect you to build new ideas based of what you just reviewed. The case exercises do not follow the tutorial. I find this extremely difficult for beginners and time consuming. Be prepared to research Javascript on the net and other books along with this one.