Bests & Worsts Reviews from Amazon

according to people

401
people found this helpful, as of 2023
ranked #52,852 most helpful out of 571,544,897 reviews
★☆☆☆☆
The more I read it, the more I hate it.
First, please note that many of the 5-star reviews are written by experienced Flash professionals, who already have actionscript expertise -- and that makes them poor judges of how clear this book will be to a beginning audience. The book is explicitly written for beginners, but the authors often have a poor grasp on what readers know. On one page they start talking about "trapping" events. What does that mean? Who knows? I have a good math background, so I was able to decipher the math chapter, but it contains explanations like, "A radian is the angle of a circle subtended by an arc along its circumference that is the length of the circle's radius (hence the name, radian)." What's the point of writing a sentence like that? Will it be understood by anyone who doesn't already know what a radian is? Has a math newbie even ever heard the word "subtend"? This casual use of undefined jargon happens in every chapter. Also, sometimes they're just wrong. They say that a ball moving 4 pixels to the right and 4 pixels down per second will have a velocity of 4 pixels per second in a south southeast direction. No. The Pythagorean theorem (which they explain, badly, in the next section), says the ball will be moving more than 5.6 pixels per second. And the direction is southeast. The book really is full of typos, and they're not all caught in the errata. The only way to know if the code is correct is to to go the website and download the code being discussed in the book. The files you download will have the correct code (though before you check the code, as you're reading the book you're thinking, "Do I not understand, or is this code wrong?") Unfortunately, the book sometimes refers to these files by the wrong name, so you have to figure out which file to open. That's really inexcusable -- how hard would it be for the authors to go to their own website and correctly name the files? Another random, infuriating example of the book's sloppiness: on page 144, the authors state a line of code "g.curveTo(275, 0, 400, 100);". In the context of the chapter, the hardest part of this code to understand is the "275, 0" and it's the one part they don't bother to explain! And as long as I'm ranting (I just threw the book down to come and write this), the authors often put unnecessary lines into the code. I'm left trying to figure it out, wondering, "Why did they put that there? Is it necessary?" so I try the code without the extra material, and it still works fine. But the authors never explain why it's there, so while you're trying to learn to read actionscript, wanting to understand the importance of each line and its relationship to the rest of the example, you're thinking, "Am I just missing the importance of this line? Or does it have no importance?" Learners shouldn't be left to wonder those things! It's a maddening book, full of unexplained terminology (I just found the phrase, "dedicated canvas"; huh?), incomplete explanations, bloated code, and many, many errors.
April 2008 · Books
the product in question
Learning ActionScript 3.0: A Beginner's Guide
4.3★ · 111 ratings, as of 2023
worser bester