3 ms·
If there is one book every JS developer should get it's "The Good Parts". Completeness is not the same as 'bestness'. Doug's book tells you what you should kn
by sh1mmer 17y ago
If there is one book every JS developer should get it's "The Good Parts".
Completeness is not the same as 'bestness'.
Doug's book tells you what you should know, Flannigan's book tells you what you can use.
- axod 17y agoI disagree 300%. "The good parts" is opinion and commentary. It's not fact. I want hard facts about what the language permits. I can make my own mind up about what is good and what is bad thanks. "The good parts" is an interesting read once you know the language, but I certainly wouldn't recommend it as a first book on js.
- sh1mmer 17y agoIn that case please don't read any books about patterns, or best practices. You might be the best programmer on HN for all I know, but personally I'm willing to admit Doug's decades of programming and international reputation might mean he can teach me something, without me having to learn it the painful way.
- axod 17y ago>> "In that case please don't read any books about patterns, or best practices." I don't. I hate naming things as patterns with a passion FWIW. I'm not really sure you can really learn good taste from a book :/ All you need is the language reference, and years of practice...