Being a fan and being inspired
When I first started reading about Douglas’ mindset and ideas, and seeing him doing a live presentation, he immediately felt very right on track. Extremely experienced, almost to the extent that some find him cynical or bitter, but if people just read/listened to what he says more thoroughly, they’d find out that he tears something down to able to become constructive and truly inspiring at the end.
The book consists of 10 chapters and 5 appendixes:
- Chapter 1. Good Parts
- Chapter 2. Grammar
- Chapter 3. Objects
- Chapter 4. Functions
- Chapter 5. Inheritance
- Chapter 6. Arrays
- Chapter 7. Regular Expressions
- Chapter 8. Methods
- Chapter 9. Style
- Chapter 10. Beautiful Features
- Appendix A. Awful Parts
- Appendix B. Bad Parts
- Appendix C. JSLint
- Appendix D. Syntax Diagrams
- Appendix E. JSON
I bought this on pre-order and received it a couple of weeks ago. I've not read it – but I did suspect it was going to be mostly things I already knew.
I think it was more to hammer home some of Crockford's approaches. Cheers for the review, it's encouraged me to get back to the book!
"Lost" references in the code samples? I totally need to read this book. 🙂
JSlint is not perfect, and there are a lot of scripts that fail in JSlint, but are written truly correctly.
My cent, for a book that I’ve not read, yet 🙂
But the module pattern? What does that say about your personality: marking private methods with underscore in my perfect code is not good enough, I must prevent other coders from ever ever being able to touch my private parts. I must remove the theoretical possibility of ever touching them, for the benefit of inferior coders that don’t understand the concept of private. Not even when the nuclear power plant is about to melt down should you do a quick fix with my perfect private code. It feels more like C++ or ADA than a good coding practice for a modern dynamical language.
Good that I got you back on track then! 🙂
Ha ha! Yep! 🙂
Well, there are some things that can be discussed, and absolutely, it's based on his conclusions. But I'd say about this book at least, is that he doesn't bring Yahoo or YUI forward in any way, and it is indeed written in an very general fashion.
Glad that you've been inspired by Douglas!
First and foremost, I find it most important for everyone in the development team to agree how they should write good, and, naturally, feel good about it. Personally, I like the module pattern because it makes for a clear separation in the code about what's private and what's public.
When developing a web site shared with a lot of other web developers, bringing in code from an external source you can't control or offer your code as a public API, I think it's a good approach to avoid that key aspects in your objects aren't overwritten.
PS. I really like the idea of stix.to DS.
Since it was Douglas I learned it from Douglas in person, when he explained the inner workings and thoughts behind it. He was promoting it and thought that most people should start using it.
I'm not really claiming that he invented it, or have no input from others with working with it, but rather just that it was him I learned it from.