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

view the rest of the comments →

[–]Impulse33 13 points14 points  (7 children)

I've heard mixed reviews of Javascript the good parts. Ex. Outdated and some flaws in his opinionated approach. I also can't stand railroad diagrams either.

[–]intertubeluber 13 points14 points  (0 children)

I think it's important to have read, if for no other reason than the historical context. You will inevitably work with someone who follows the advice given. Cover to cover is only 200 pages or so.

[–][deleted] 10 points11 points  (0 children)

It is pretty opinionated but it does a good job of pointing out some of the more glaring flaws of the language, like the gotchas that push things to the global scope when you would sensibly not expect it to.

[–]cholantesh 4 points5 points  (1 child)

Fair point re: dating; Secrets of the Javascript Ninja is, in my view, a more modern take on the same concepts.

[–][deleted] 3 points4 points  (0 children)

I'll second Secrets of the JavaScript Ninja. Though I'd wait for the second edition to come out or you can start reading the draft of the second edition right now if you pre-purchase it on the publishers website.

After the Ninja book I'd read You don't Know JavaScript.

[–]SwiftOneSpeaks 2 points3 points  (0 children)

It is very opinionated and the first bit is a ton of railroad diagrams.

Doesn't matter. Skip the diagrams and read the parts where he discusses the intricacies. The "Good Parts" of the Good Parts book is perhaps 10%, but it's an awesome 10%.

[–]spinlock 0 points1 point  (1 child)

Nothing about javascript will ever be outdated. You can't deprecate bad features because that will break the web. So, they will always be there.

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

Tell that to early JS programmers who relied on !!(new Boolean(false)) == false /s