by dannygarcia on 2/6/14, 5:02 AM with 23 comments
by shadowcats on 2/6/14, 8:16 AM
But maybe that is just par for the language course, before one even starts to wants to master Engineering :)
JavaScript: The Good Parts - http://www.amazon.com/gp/product/0596517742/ref=as_li_ss_tl?...
Here's a few other good ones:
Functional JavaScript: Introducing Functional Programming with Underscore.js - http://www.amazon.com/gp/product/1449360726/ref=as_li_ss_tl?...
Secrets of the JavaScript Ninja - http://www.amazon.com/gp/product/193398869X/ref=as_li_ss_tl?...
Javascript Allongé (free to read online) - https://leanpub.com/javascript-allonge
Javascript Spessore (free to read online, but currently work in progress) - https://leanpub.com/javascript-spessore
Here's a good one about Angular, my favorite framework:
Mastering Web Application Development with AngularJS - http://www.amazon.com/gp/product/1782161821/ref=as_li_ss_tl?...
I would of course also recommend the Egghead videos for any Angular aficionados: http://www.youtube.com/playlist?list=PLP6DbQBkn9ymGQh2qpk9Im...
PS. The Amazon links are affiliate links.
by akbar501 on 2/6/14, 10:13 AM
Any serious JS dev needs to master async.
2. Functional JavaScript: Introducing Functional Programming with Underscore.js http://www.amazon.com/gp/product/B00D624AQO/ref=kinw_myk_ro_...
While the book uses Underscore, that's not its focus. A good understanding of functional programming and when it can be useful is a valuable skill.
by kabdib on 2/6/14, 1:25 PM
Or, if you have to read it, please realize that everything does not need a factory, and you almost certainly don't want to have nested and indirect factories (I have three letters for you that should be terrifying: COM), and that not every piece of code you write needs to be from The Book of Patterns, and in fact if you do find yourself leafing through TBoP in search of a pattern to use, you're going about things all wrong and your cow-orkers will hate you and string you up for Pattern Abuse and the best thing that can happen is that you'll look at your code six months from now and say to yourself, "Ewwww, this crap has got to go."
by raganwald on 2/6/14, 7:50 AM
Also, leave the affiliate links in. Those who care to remove them know how to change the affiliate code to benefit their favourite charity.
by chadillac on 2/6/14, 6:03 AM
by minusSeven on 2/6/14, 7:09 AM
by brickcap on 2/6/14, 2:21 PM
https://developer.mozilla.org/en-US/learn/javascript
Besides tutorials on mdn they have included links to some of the best javascript resources on the internet and classified them according to the level of the individual. It was very helpful when I was starting out in javascript and I still go back time to time to refresh some concepts
by hopfog on 2/6/14, 12:40 PM
It explains all aspects of JavaScript in a very clear and concise way and contains the best description of the prototype chain and inheritance in JS I've ever read.
by WillPiner on 2/6/14, 7:09 AM
by hugofirth on 2/6/14, 11:47 AM
I love CLRS but am always up for increasing my knowledge base when it comes to algorithms. Has anyone read both?
[1]: http://en.wikipedia.org/wiki/Introduction_to_Algorithms
by quarterwave on 2/7/14, 11:32 AM
Specifically: (i) how to leverage Javascript to write better networking code (e,g; cluster, websockets, etc), and (ii) for number crunching on the server-side, should the relevant code be written from scratch in functional Javascript, or is it better to fork a process that runs (say) Julia code?
by ojr on 2/6/14, 10:27 AM
by illamint on 2/6/14, 4:32 PM
by wila on 2/6/14, 1:12 PM
by MadMaddie on 2/6/14, 3:57 PM
by platz on 2/6/14, 7:45 AM
by vvvVVVvvv on 2/6/14, 11:53 AM
Hmmm yeah, sure.
by renownedmedia on 2/6/14, 5:58 AM