Learning Ecmascript 6

I don't like giving things a bad review, but I'm extremely disappointed with the quality of this book and if I weren't lazy, I'd try and get a refund.I regularly and heavily read programming books and text-books and am rarely disappointed. Even if a book doesn't really fulfill my needs I usually appreciate it as long as it is professionally made and has decent content (basically, as long as it would have helped somebody).Getting down to it, the writing in this book is shoddy; there are errors in the English all over the place. There are missed plurals, completely missing words, and extremely awkwardly (at best) written sentences throughout the book (though most pages read alright; inconsistent reviewing?). Worse yet, the content is not even very useful.Much of this book reads more like a poor-man's Java-Doc than a text-book. I just got to chapter 7 and the last chapter was basically "Hey, ES6 has a better reflection API, here's the fifteen functions and brief descriptions of them in order with minimal examples. The only real use cases or justifications for why these things even exist or are useful are on a single page at the end in bullet-point form like they were added lazily when someone complained about it. So, you don't know who would use them for what or why. At least a few of the earlier chapters followed the exact same pattern as well, and it gets more frustrating with every passing chapter.Even the few key ES6 topics, e.g. promises, are not well managed. They clearly paid more attention to key topics and provided extra examples, but they favor silly examples with tons copy-paste for the sake of very minor modifications over any real content. The end result is you can read it without extracting much value.Anyway, sorry for the rant; but I felt gypped on this one.

Great way to shift from ES5 to 6

a

I feel bad giving this a two-star review.There are countless ways to learn ES6 (now ES2015) online. I like books, though. So, I got this book because it was a book, and I wanted to learn more about ES2015 from a book.I really don't want to insult the author or its reviewers. They're all clearly competent developers, and the book treats a lot of interesting topics. However, it also reads like it skipped several rounds of copy-editing. The english is incredibly difficult to parse at times, and there are *a lot* of minor (but annoyingly frequent) syntax errors in the code samples (e.g., "Var" instead of "var", missing spaces after certain keywords, etc.).I'm 100 pages in, and I feel like I significantly overpaid for this book. That being said, I'm still learning things.

Clean and easy to follow. A good primer for grasping the concepts behind new ES6 syntax and methods.

This book was clearly not edited thoroughly--or at all for that matter--and was very poorly written (I don't intend to be mean, I'm trying to be as accurate as possible, especially considering I'm a fellow educator in the programming arena) . Proper grammar and clarity are an important part of educational materials and neither should be overlooked. The writing is so poor to the point that it's cognitively taxing to follow what the author is saying. The code examples are also so basic to the point that they aren't effective, not to mention there is no scaffolding in this book whatsoever.

I read this book on Safari books online. It gives a technical overview of the new features to the language. If you go with the quote from Albert Einstein that "If you can't explain it simply, you don't understand it well enough" then this author does not understand the changes well.The problem with this book is that the descriptions of the new functionality are often vague, missing or just unintelligible. The code examples explain things way better than the author's description. For example, consider this vague wording from a section of the book: "If a constructor is invoked via super keyword, then the value of new.target in it is the same as the value of new.target of the constructor that is called super." Much of the book is written like this.One glaring issue with the book is that there is no description of why a new feature was introduced or why you would want to use it in your own JS development. For example, Symbols were added to ECMA 6 but the author fails to really tell why they were added and for what uses cases you would want to make use of them. In my opinion, knowing the "why" is much more important than knowing the "what" of a language feature.Overall I do not recommend this book and hope that there are different books on the subject out there that are more intelligible.

I’ve read some of the poor reviews for the book, but I didn’t think the book could really be as bad as they made it out to be. I was wrong.The text is painful to read. Nearly every sentence has a grammatical mistake or is at least awkwardly worded, often making it difficult to understand the author’s meaning.Furthermore, the code isn’t written well. There are problems just in the first few pages. The author states, “it is recommended to switch to using the let keyword”, and yet just a few paragraphs later there’s an example (showing usage of the const keyword) that uses var.A few pages further, when discussing default parameters, there’s an example of how default values have supposedly been traditionally assigned:x = x = = = undefined ? 1 : x;And yet in JavaScript, that would have typically been written as:x = x || 1;Not only was the text written poorly, but the code examples were too. I gave up on reading it.

Can't fault the technical content, but the grammar makes this book hard to read. So much so I abandoned the book after a couple of chapters and followed an online tutorial instead. With so many reviewers I would have expected someone to pick up on the over use of "the" and "a" and the amount of unnecessary repetition.What did the editor do when the book was submitted? If they read it I can only assume they were not a native English speaker.

This should never have been published and is a shame on the publishers. There are errors in correctness, syntax, grammar, spelling and structure. One trivial example: DataView is sometimes spelled DateView and neither is indexed. It is the first time I have ever asked for a refund on a book.

Full with knowledge. Need some more improvement.