- Regular expressions
- Beautiful features
Most helpful customer reviews
593 of 606 people found the following review helpful.
By Frodo Baggins
Do you find the syntax to be non-intuitive and frustrating?
Do you know the difference between using a function as an object vs using an object literal?
Do you know how using object literals can simplify your code and create something similar to namespaces?
Do you know how to augment the type system -- for example, if wanted all strings to have a trim() method?
Do you know why the "new" statement is so dangerous? Do you know an alternative that eliminates the use of "new" entirely?
These are some of the topics that the book touches upon.
You might ask "Isn't this stuff already covered in other books that I have?" The answer is no. For one, most other books use a psuedo-classical coding style (see below) to explain objects that is a source of confusion.
There are a series of Yahoo! videos by Crockford that mirror the material in this book and can be found as podcasts under YUI Theater. They contain nearly all of the material in the book and probably a little more. Those videos are:
- Douglas Crockford/An Inconvenient API: The Theory of the DOM (3 parts)
7 of 7 people found the following review helpful.
Classic JS book that every JS dev should read and reread.
This is one of the classic JS books that every JS developer should read.. and read multiple times. personally I think Ive read it about 4 times. There are lots of reviews on this book and just as many opinions about it. Regardless of all of those, you have to give Crockford the credit for helping to take JS to a new level that most JS devs were not thinking about at the time of its writing. There is a lot of "cowboy" coding in the JS world and this book was one of the first successful books to start defining *best practices* for JS coders. You will find the influence of this book in many other resources and software tools and undoubtedly tech discussions that you get in. The book is opinionated on some things and I get it that this bothers some people. If it bothers you then I say, "Have the sense of a cow... eat the hay and leave the sticks"... then read it again in a year and see if your opinion changes. Definitely a MUST READ for any JS dev.
8 of 8 people found the following review helpful.
See all 568 customer reviews...
Kindle edition riddled with errors dating back to 2008
By Michael Stanford
I also like the explanations: how and why the good parts work. But this is where I begin to have reservations about the book. Some of the explanations are incomprehensible because of poor editing. How is it possible that a collection of technology pace-setters (Crockford, O'Reilly, Amazon) can leave numerous "confirmed serious technical mistakes" in their work uncorrected for at least 4 years (I bought it in 2012)?
O'Reilly's errata website for this book lists 157 'confirmed' errata, of which 9 are classified as "Serious Technical Mistake." There are also 22 "unconfirmed errata." Most of the confirmed errata were marked as fixed shortly after publication, but at least one of them ("beget") is still in the Kindle edition. O'Reilly helpfully provides downloadable copies of the example code online, but the current version still contains errors that prevent the code from running (mode/node).
I keep going back and re-reading this book, so looking past all my wasted time trying to make sense of the errors, I would give a correctly edited edition of this book five stars for the educational insights sprinkled through it. Or maybe not any more. The state of the art has changed. For example, as many one-star reviewers point out, the whole section on Object.create is outdated. This book needs a rewrite.