3 ms·

asides from ES5 and promises , none of these are core javascript issues. NodeJS is not javascript , CommonJS what the hell is that ? nobody cares about that stu

by camus 14y ago

asides from ES5 and promises , none of these are core javascript issues. NodeJS is not javascript , CommonJS what the hell is that ? nobody cares about that stuff , HTML5 is a set of apis , nothing to do with javascript , If i want a book on javascript i want a book on the language itself , not on canvas , webgl, requireJS or Express or Backbone ...

jQueryIsAwesome 14y ago
False, you want a book plus its applications; if you buy a book about woodworking you probably want to see some examples of furniture creation and other practical challenges to apply your new found knowledge. That is why this book deals with DOM and BOM from chapter 11 to 15 even if those are not purely JavaScript.
k3n 14y ago
> asides from ES5 and promises [...] CommonJS what the hell is that ? 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 http://wiki.commonjs.org/wiki/Promises 2. http://www.commonjs.org/specs/ 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...
- deleted 14y ago
  [deleted]
lnanek2 14y ago
Core or not, I'd prefer coverage of those issues myself. I can't really think of core problems I run into myself, I've been writing core JavaScript for a decade or something, but there's lots of intricacies with those other things where I wouldn't mind tips. Different audiences, I suppose. I browsed the TOC one kind reviewer was nice enough to list, saw there wasn't anything I was interested in or had trouble with lately, and moved on.

by camus 14y ago

jQueryIsAwesome 14y ago

False, you want a book plus its applications; if you buy a book about woodworking you probably want to see some examples of furniture creation and other practical challenges to apply your new found knowledge. That is why this book deals with DOM and BOM from chapter 11 to 15 even if those are not purely JavaScript.

k3n 14y ago

> asides from ES5 and promises [...] CommonJS what the hell is that ? 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 http://wiki.commonjs.org/wiki/Promises 2. http://www.commonjs.org/specs/ 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...

deleted 14y ago
[deleted]

lnanek2 14y ago

Core or not, I'd prefer coverage of those issues myself. I can't really think of core problems I run into myself, I've been writing core JavaScript for a decade or something, but there's lots of intricacies with those other things where I wouldn't mind tips. Different audiences, I suppose. I browsed the TOC one kind reviewer was nice enough to list, saw there wasn't anything I was interested in or had trouble with lately, and moved on.