JavaScript The Good Parts

The book is widely praised for its unique and insightful approach to JavaScript, aiming to legitimize it as a serious programming language rather than a "toy." Many reviewers highlight its ability to broaden horizons and evolve a developer's way of thinking about the language, offering a perspective born from deep, long-term experience with JavaScript's intricacies. It is valued for distinguishing which parts of the language should be used and which avoided, providing invaluable precautions against subtle pitfalls that even experienced programmers might overlook, such as those related to automatic semicolon insertion. Readers appreciate its honest identification of JavaScript's "deformities" and its focus on extracting a "shining core" of good practices, often inspired by the author's own JSLint tool. The book is lauded for being terse, clear, and packed with useful information, helping developers understand how JavaScript truly works, avoid common errors, and write more reliable, robust code. Its concise nature and high value-for-word ratio are frequently cited as significant strengths.

Despite its strengths, the book faces criticism regarding its target audience and explanatory clarity. While it claims to be for developers new to JavaScript, many reviewers found basic concepts poorly explained and deemed it unsuitable for programming novices, suggesting it would confuse beginners. A significant portion of the book is dedicated to syntax flowcharts, which many readers found to be an inexplicable waste of space and unhelpful for human comprehension. Critics also point out that the author's recommendations, such as avoiding certain common operators or advocating for strict equality, are sometimes presented as strong personal opinions without sufficient rational arguments, occasionally coming across as obsessive or dogmatic. Furthermore, a common criticism is that the book, originally published in 2008, contains information that is now outdated or discusses language limitations that have since been addressed in newer ECMAScript versions. Some found the overall organization strange, with important insights relegated to appendices and a lack of a cohesive learning narrative for its core "good parts." Issues like bugs in code examples and a sometimes condescending tone were also mentioned.

In conclusion, this book is considered a classic and a must-read for anyone serious about JavaScript, offering a transformative perspective on the language. However, it is emphatically not recommended for complete programming beginners or those new to JavaScript without prior foundational knowledge. Instead, it is best suited for experienced programmers who are familiar with general programming concepts and are seeking to understand JavaScript's deeper mechanics, avoid its pitfalls, and adopt best practices. While some content is now dated, and its unique structure and strong opinions may not appeal to all, its core insights into writing quality, reliable JavaScript code, including discussions on object-oriented patterns and closures, continue to be highly valuable for intermediate to advanced developers looking to refine their understanding and approach to the language.