views:

124

answers:

3

Definitely, Crockford's book: "JavaScript: The Good Parts" is one of the best books in Javascript. However, it is hard to read. I have spent hundreds hours but still cannot understand it completely. Maybe it is not because of Crockford but Javascript itself.

I don't care the Good Parts of the book now, but I want to know the Bad Parts of the BOOK, because the Bad Parts of the book is also important.

A: 

Pages 101 - 114 discuss the bad parts. You can see here on Google Books

Shane Reustle
I want to know bad parts of the book, not bad parts of Javascript
John
+1  A: 

No bad languages just bad programmers.

dryprogrammers
Really? Have you ever looked at the syntax of the admittedly useful AutoHotkey?
Matthew Lock
+2  A: 

but still cannot understand it completely

I think you're reading the wrong book at your level of understanding. The book itself says that it is not designed to teach javascript and it expects readers to already understand everything it discusses.

Its only mission is to discuss (explain rather, Crockford is very opinionated) WHY doing things some ways are better than others.

To be honest. I've not yet found a good introductory book on javascript (and if you don't understand closures and prototypes you are still at the introductory level no matter how long you claim to have been programming in javascript). The closest that I've found to being good is The Rhino Book. Or if you prefer practical examples then PPK on Javascript.

slebetman
Thanks for the links, helpful
Danjah
Rhino +1..................
Matthew Lock
I agree it is a good book, and I learned a lot, but I don't want to repeat the good parts. However, I still cannot understand the book completely. Do you understand the book 100%? And find all parts of the book are good? I guess some people, like me, are struggling with some parts of the book. Hopefully, my question will bring discussion of these "bad" parts.
John
@John: I understand the book completely, and my main issue with it is that there are some inaccuracies. I also disagree with several of Crockford's opinions. Overall, though, I think Crockford's done a lot of good getting developers thinking seriously about JavaScript and his book is a good summary of his ideas.
Tim Down