To say that I was doing Javascript without being aware of all that ...

JavaScript is a language that contains many ideas, and historically it has some baggage. Falling on "concerns" is simply inevitable. In any language for that matter. Open to these problems we could say that it's a little part of the programmer job than knowing avoid lending, anticipating their inevitable and inevitably painful amplification after Murphy's Law (I checked in practice even though it is more accurate to say "experienced" and not catch me).

I think that anyone developing for the web has had its share of unpleasant surprises Javascript. And, comparing with other languages, I think do not be the one to tell me still Javascript has more than its share of problems.

So this is a book that offers an interesting perspective. But I believe it is essential. Indeed Javascript was synonymous to boost its web pages. This is less the case today but it's still its main purpose. And it strongly tint our practice of language: ultimately, we especially seek specific solutions. Given the differences between browsers, we turn one day either to Javascript frameworks (usually very early). To sanitize even the code I use for my part JSLint, tool created by the author of this book elsewhere. For frameworks are frameworks and can not change (usually) the language in which they are based. The remaining ingredient is practice to develop some autonomy and effective methodology.

Nevertheless, all this is beating around the bush. Even with the right credentials language available on the Internet, I have not passed the mastery of language, the one where you will check the documentation and forums for a detail that has escaped you, or a new situation. Well that's what allowed me the book of Mr. Crockford finally pass this course.

If we start from the Chapter 3 -Objects- Appendices A and B to the (Awful Parts and Bad Parts), you have a summary of less than 100 pages on what the author considers to be excellence in Javascript. Obviously this is subjective. But it's damn relevant and comprehensive, rather, to only 100 pages, the game is worth the candle. Frankly, the first thing I did-because I was not 100% convinced by the subject-it was read Appendices A and B: 14 'awful parts' and 12 'bad parts'. Well, even if you do not agree with subjective categorization of the author, you realize how plasters should be dry before settling on a stable base!

Douglas Crockford has done this work and it has been well documented with this book. It would be a shame to miss. Especially since Javascript is clearly one of those rare languages ​​that may remain for a while.