The content is very useful, and written by someone truly competent. But he deserved to be a little more detailed (chapter "9" on the "style" is a blatant example of "put there because the author has thought of something."
The organization of the book itself is a bit poorly made, with a lot of annexes, some of which have made good chapters, while some ridiculously small chapters would have been better in the appendix.
Book interesting points:
- List many elements of Javascript, explains how they work, and especially the problems they can cause.
- Indicates a solution to every problem, and even specify how to do without the item.
- The various components are described using a flow chart: just follow the arrows to realize how, for example, a particular command (function, method, etc.), and all lights then very quickly.
Summary:
Chapter 1:
Why this book ... A little abused write a chapter just for that.
Chapter 2:
How the different elements of language: numbers, names, spaces, channels, statements, expressions, literals and functions.
The author explains each element using a diagram, actually, if one takes the time to study it, shows how well it will work. This may even help understand mistakes, and in any case to do less.
Chapter 3-7:
Each chapter then discusses a particular element: objects, functions, inheritance, arrays, regular expressions,
How they work, how to create them, how we delete, modify, etc. The author explains what are the differences, for example, for the object, what a prototype, invocation, exception, etc.
Diagrams are still in the game.
Chapter 8:
Methods.
This part is duplicated with a manual, I think. Examples of implementation are given, and the author emphasizes some problems that may be encountered.
Chapter 9:
The style. On page four (yes, the chapters are unequal in length VERY) few tips on how to program "cleanly" and avoid various problems.
An interesting chapter and so light compared to any web page that is limited foutage of mouth. But it's still interesting, and especially contradicts most teachers :-p info (like most experienced programmers, in fact, teachers are not very interested in good quality code, but by the ability to " produce fast ")
Chapter 10:
Even a very short chapter (three pages), where the author tells a story about how he was forced to make some choices about the functionality of the code. Informative.
Appendix A:
A dozen pages entitled "horrific elements," which lists what's not in Javascript, to the point of being dangerous, and how to avoid problems (none of this was seen during my first year of During dev CNAM ...).
Appendix B:
6-7 pages on less dangerous than the preceding, but anyway poorly designed, and how once again avoid the problems (m. That also not seen. But I had these courses for what, actually?) .
Appendix C:
Description and instructions (light) of JSLint, auditor of javascript code.
Appendix D:
A list of diagrams showing the operation of various JS elements. Very clear, useful, but again we must make the effort to read (it can seem daunting).
Appendix E:
JSON. What it is, how to use it without opening major security holes like this and example code using it.