Disclaimer: because of my affiliate relationships, you will make me money if you click on any of the book links below, then buy a book.
This is why whenever I try to learn a new computer skill, I’ll buy a book about it first. Books go through rigid editing processes like fact checking and proofreading, all helping to filter out the bad content.
cloneNode(), but aside from the object literal, there no mention of design patterns.
A few things: OOJ was published by Packt Publishing who is notorious for releasing books with grammatical and spelling errors-this book is no exception. If you buy it, go to Packt’s Support page, click on the “Title” drop-down menu and find the book title: you’ll see the errors.
Also, Stefanov is working on the 2nd Edition of this book. He’ll be tackling ECMAScript5 and will have a new chapter on JS testing and documentation.
Another Stoyan Stefanov book, this one explains some excellent best practices such as the right way to structure for loops, when to use
This book also drives home the importance of keeping the global space as clean as possible. Stefanov’s tips on namespacing patterns, inheritance and encapsulation are must-learns.
new keyword, switch/case statements…be prepared to throw some of these away.
I’ll be completely upfront here: I’ve read most of this book, but not all of it. Plus, I haven’t implemented a lot of the new stuff I learned from it.
A suggestion on how to read these books
To be honest, I suggest that you read Patterns and The Good Parts in parallel with the first two books. For example: when you start to read about for loops in Visual QuickStart Guide, take a few minutes and see what both Patterns and the Crockford book say about them. This is a pain, but the sooner you learn these best practices, the better.
After all this, go back and read Patterns and the Crockford book in full.