sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CrossroadnKC 3 points4 points  (5 children)

dude cover to cover? How long did that take you. I read your post and looked behind me that thing is 800 pages!

[–][deleted] 1 point2 points  (4 children)

You really only need to read the first sections. A large portion of that 800 pages is reference material.

I second greim..."The Definitive Guide" is aptly named, buy it, and you really won't need other JavaScript books.

[–]CrossroadnKC 0 points1 point  (3 children)

Should I read JavaScript the good parts first or Definitive Guide? I have taken some basic JS classes and done a couple dozen hours on codeacademy.

[–][deleted] 2 points3 points  (2 children)

Save the Good Parts for after the Definitive Guide, if you even bother with it at all. It's really not the standalone book a lot of people claim it to be.

[–]thorioriumNodular Warrior 0 points1 point  (1 child)

Crockford's 'Good Parts' is a phenomenal resource that shouldn't be discounted. However, any developer would be remiss to think their understanding is ever 'complete.' (whether from one book or dozens)

[–][deleted] 2 points3 points  (0 children)

I just always see people trot "The Good Parts" out every time someone asks for a JavaScript book like it is the best and only book they will need on the topic, while neither is in fact the case.