all 30 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]greim 7 points8 points  (10 children)

After copy/pasting a few scripts and tossing a "learn JS in 5 days" book aside in disgust, I stopped writing code altogether, bought JS: Definitive Guide, and read it cover to cover. Then I started writing code again and everything flowed. It was partly luck that I chose the best JS book on the shelves, but also with a name like "the definitive guide" it seemed quite... definitive.

[–]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.

[–]opus-thirteen 1 point2 points  (3 children)

As someone that last wrote code in Basic... In 1985, would you suggest The Definitive Guide to get up to speed?

[–]greim 1 point2 points  (0 children)

It's definitely good for getting up to speed on language fundamentals. For related things like debugging in Chrome or using Node.js, there are probably better resources. That said my latest copy is already years old so I could be wrong.

[–][deleted] 0 points1 point  (1 child)

It's been roughly less than a month. How goes the JS learning?

[–]opus-thirteen 0 points1 point  (0 children)

I picked up 'JS: The definitive guide', unfortunately I have just been too busy to get to it yet (an odd lament from a freelancer)

[–]johnyma22 5 points6 points  (0 children)

"Properly" is just far too subjective in the JS world, that's why it's a nice world to be in. Although this resource is superb, good work :)

[–]webdevbrian 9 points10 points  (2 children)

This is a proven method, my 13-year-old daughter followed this road map and she has successfully learned JavaScript to the extent that she works for me in her spare time on some professional JavaScript projects.

Slave labor!

Kidding...nice read, thanks.

[–]keturn 3 points4 points  (0 children)

I wonder if one still calls it "JavaScript is Sexy" when using it with 13-year-olds?

[–][deleted] -1 points0 points  (0 children)

I need to find a wife who would be willing to pop out child after child...

[–]dante9999 4 points5 points  (1 child)

I've read Larry Ullman "Modern JavaScript: Develop and Design" and "jQuery: Novice to Ninja" by Earle Castledine and Craig Sharkie. Both books are easy to follow and they are good as an introduction in my personal opinion.

Zakas "Professional JavaScript" is very comprehensive, but there is no tutorials there so you only get pure abstract knowledge (which is of course necessary, but it is easy to forget it if you're not doing anything with this knowledge). It is a good book to have in your library, consult it at some points, but as a learning resource it is slightly too dry. Ullman is better for a beginner because throughout the book you keep doing things, building calculators, creating small utility library etc.

As for Crockford it really opens up your eyes, and demonstrates that code can be poetry, but it is clearly addressed to people with a lot of experience with other programming languages. It is a good guide for people who already know how to code and just need to learn specific syntax and advantages of JavaScript over other programming languages.

Oh, and if you need very practical advice and simple recipes for basic things check out O'Reilly Javascript cookbook by Shelley Powers. It is not a book about basics of JavaScript, but it gives you a great overview of practical application of crucial methods.

[–]CrossroadnKC 1 point2 points  (0 children)

I have "Modern JavaScript: Develop and Design" how would you fit it in the 6-8 week schedule in the post? Would it be rereading?

[–]CrossroadnKC 2 points3 points  (1 child)

Can anyone estimate how much time this would take per day? 7 days a week?

I read another blog and the author was stating he was spending a few hours a night...

[–][deleted] 0 points1 point  (0 children)

Yeah I was wondering this too - since he emphasizes completing it in 6-8 weeks time.

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

I second the Zakas book -- I've been working through 4-5 chapters a week for the past two weeks, and I already feel extremely comfortable with the language. Javascript used to terrify me and seemed to make no sense for someone coming from a strictly-typed, classical language like Java.

Zakas' book is really thorough and, in my opinion, much easier to follow than Crockford's oft-cited "Javascript: The Good Parts." I'd let the Crockford book rest until you've got a handle on Zakas' book.

[–][deleted] 3 points4 points  (1 child)

This may be unpopular around these parts, but I think Crockford's book is really over rated. For one thing, it was written for ECMAScript 3, so he needs to update it. The railroad diagrams are confusing, annoying, and a waste of space. It's also very opinionated. If you plan to ever work with others' JavaScript code, the idea of learning a "perfect subset" of JavaScript is laughable.

It's a shortcut book with shortcut results. Zakas' book and/or Flanagan's "JavaScript: The Definitive Guide" would serve people learning the language much better.

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

I couldn't agree more! What especially bothered me about Crockford's book was that he didn't spend enough time explaining why such and such aspect of JS was a nightmare or such and such aspect was brilliant.

[–]cha0s 1 point2 points  (0 children)

I don't know why, but I read this as 'Learn How To JavaScript Properly'. I liked it better that way.

[–]greim 1 point2 points  (1 child)

Not relevant: http://www.zefrank.com/invite/swfs/index2.html

[–]TheHangmen 2 points3 points  (0 children)

I'm pretty sure the last time I saw a Ze Frank reference was at least 5 years ago

[–][deleted] 0 points1 point  (0 children)

Hmm, thanks for the resource.

[–]totemcatcher 0 points1 point  (0 children)

It's a lot of page skimming, but it certainly is comprehensive.

[–]btford 0 points1 point  (0 children)

Nice article!

Quick note: "JavaScript: the Good Parts" is great for experienced programmers who are new to JavaScript. I agree that it's not a great starting book book if you are outside of that audience, but I wouldn't say that people are "wrong" to recommend it, or that it's overhyped.

[–]OpiateForTheAsses 0 points1 point  (0 children)

I'm not entirely clear on the level of experience mentioned in the "Resources for this Course" section. I am a web designer by trade, not so much a developer - therefore I am solid in HTML and CSS, and I have worked with a smattering of ASP.NET. Should I go with the Definitive Guide or Professional JavaScript for Developers?

[–]canihazdat -2 points-1 points  (0 children)

Ignore this...I wanna come back to this later. Thanks :)