* ES5
* CommonJS
* promises/deferreds
* AMD/UMD/etc.
* NodeJS
* asynchronous concerns such as callback hell (and other focus areas as addressed by Async.js[1])
* packages
* HTML5
* the MV* hysteria
Granted, many of those aren't central to "JS" proper, they should at least bear a mention....but perhaps not. Just seems like what's covered is mostly run-of-the-mill JS fodder...Ugh! I have his prior book, Pro JavaScript Techniques (Apress, 2006), and that's basically how I've always described it. I refer to it as 'The jQuery Memoirs'.
Thanks for the reply, and good luck with the book! I do plan to check it out.
Perhaps you should learn what you're criticizing before you criticize it; CommonJS has put forth a lot of effort to try and standardize API's across platforms (browser, server). API's for things like...promises[1]. And modules, plus many more[2]. Ironically, several of these could very well end up in ES Harmony, and so to discuss them now wouldn't be too much of a risk because the problems they solve exist today.
1. http://wiki.commonjs.org/wiki/Promises
2. http://www.commonjs.org/specs/
> NodeJS is not javascript [...]nobody cares about that stuff , HTML5 is a set of apis , nothing to do with javascript
Yes, but if you work with JS in any capacity today, then there's a good chance you'll be working with either or both of those technologies.
> not on canvas , webgl, requireJS or Express or Backbone
I didn't mention any of those...
That is why this book deals with DOM and BOM from chapter 11 to 15 even if those are not purely JavaScript.