I decided to write an in-depth review of the book to help others decide whether or not to buy the book.
Why take my advice?
I’ve been a front-end developer for nearly 9 years, and have incrementally been expanding my skills my entire career.
Should you be learning ES6?
When I finally decided to dive in, I looked for a trusted source. I wanted detailed explanations of concepts like arrow functions, let, constants, classes, and template literals.
How I picked this book
Since that book was also written by Zakas, I trusted he would put the same quality into this ES6 book as well. The overwhelming positive reviews also gave me the confidence to purchase.
Who the book is for
Here is an excerpt from Zakas himself about who the book is for:
Who this book is NOT for
Chapters of the book
The following is a list of the chapters of the book, to give you a better idea of the concepts covered in it. I’ve also added a short description to some of the chapters, which were concepts I was eager to learn about.
- Block Bindings
This chapter gave me a solid understanding of using
constwithin blocks a loops compared to
- Strings and Regular Expressions
Template literals and better string manipulation features among other topics are covered
New ways to provide function parameters, arrow functions and tail call optimization
- Expanded Object Functionality
Updates to make it easier to work with objects
- Destructuring for Easier Data Access
Breaking down Arrays and Objects into smaller parts
- Symbols and Symbol Properties
A new type of primitive and way to create properties on Objects
- Sets and Maps
- Iterators and Generators
- Improved Array Capabilities
- Promises and Asynchronous Programming
- Proxies and the Reflection API
- Encapsulating Code with Modules
As you can see, there are a lot of concepts covered, making it a very in-depth and valuable resource. This is no quick-read at 309 pages. Rather, you can jump around to learn about new concepts and constantly revisit it to use as a reference while you learn.
I’m definitely one who learns by doing (as we all must actually code at some point), but I also find reading a book on principles, concepts and examples really helps solidify my knowledge on a subject. This book is no exception.