- Buy this product and stream 90 days of Amazon Music Unlimited for free. E-mail after purchase. Conditions apply. Learn more
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Special offers and product promotions
Frequently bought together
Customers who viewed this item also viewed
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Would you like to tell us about a lower price?
If you are a seller for this product, would you like to suggest updates through seller support?
—Erik Arvidsson, senior software engineer
—Anton Kovalyov, developer of JSHint
—Alex Russell, TC39 member, software engineer, Google
About the Author
Customers who bought this item also bought
There was a problem filtering reviews right now. Please try again later.
Having said that, I find that this book could've been more like its C++ cousins. Some items could've been abbreviated to "never do this, and here in brief is why". Instead, many items dwell on the how, why and wherefore of the misfeature, and explain in gory detail what would go wrong and when you might still use such a feature. Item 6 "learn the limits of automatic semicolon insertion" is a prime example, which drones on for nearly 7 pages. "Just don't do it already" would've done.
But, overall, there is a large amount of goodness to be had from this book, even if the odd item could've been shortened. Recommended!
But one thing that detracts from the book in some places is the layout, specifically when example code is split across pages. For instance, 3 lines of code are printed at the bottom of the page 45, and the remaining 6 lines are on page 46. It wouldn't be so bad if these were facing pages, but they're not. You can't see the entire function at one time; you have to flip the page back and forth. Surely the entire function could have been put on page 46 without destroying the layout of the book, and it would have made the code - and the point it illustrates - much more easy to grasp. It's not always possible/practical/convenient to type the code out in an editor at the time one is reading the book.