Top products from r/javascript

We found 138 product mentions on r/javascript. We ranked the 128 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/javascript:

u/adamzx3 · 5 pointsr/javascript

I can definitely relate, this sounds just like me last year! I've done things the hard way and it took me 5x longer. I also prefer screencasts to books. I always need to create a project to solidify those fresh skills, otherwise they'll be gone in a month. Also tutorials for things like Backbone assume you know how to use jQuery, Underscore, and things like REST, and JSON responses... this can quickly get confusing if your not familiar with all of these. My largest regret is not building enough practice apps in the last year. I really should have applied more by doing, instead of staying in the theoretical world.

Here are some insights that i've made and the courses/tuts/projects that helped me the most:

Learn the language first:

u/JeffreyRJohnson · 2 pointsr/javascript

Head First HTML5 Programming is a very visual book with a ton of review and quizzing and uses practical examples to teach Javascript, it's a little dated at this point, but a really great resource for book learners .

The Odin Project spends a lot of time in the beginning on teaching helpful tooling that a lot of other learning resources leave out, like git, developer tools, debugging and testing, it takes a little while to get to the Javascript part, but everything before that ends up being very useful .

Brad Traversy's Modern Javascript from the beginning Udemy course is a fantastic and thorough introduction to Javascript . Javascript has seen a lot of cool updates in the past few years, and this is one of the only courses that starts out with the "modern" approach, so you don't end up having to relearn a bunch of things . A great course for video learners .

Practical Javascript,A great course that teaches entry level javascript with practical examples that build on top of each other to form a full project . The paid subscription is a fantastic course that goes into a lot of important subjects often skipped in other courses, but can at times be very boring .

Other resources you're likely to be referred to that I somewhat disagree with

Free Code Camp & Codecademy, if you were instead learning to draw, the teaching methods of these courses would be the equivalent of tracing pictures you liked . Free Code Camp has a really great and helpful community built around it though .

You don't know Javascript & Eloquent Javascript really are some great books and deserve their praise, they're just not the friendliest introductions to Javascript if it's you don't already have some knowledge of Javascript or other programming languages .

Javascript & jQuery by Jon Ducket, this book is fine, but I just don't feel it's as good of an introduction as any of The Head First books, while still being just as dated. It is a lot more comprehensive though, but it doesn't build to a project, use as practical of examples or do as much hand holding .

u/brotherMotty · 3 pointsr/javascript

I stand by this roadmap, especially because I tested so many different free courses online (and subsequently wasted a bunch of time). Hopefully someone will find this useful.

Rithm (

  • Awesome for going from 0 to beginner/intermediate; possibly the best fundamentals I've found

  • Doesn't hand hold so it teaches you how to think

  • Writing is friendly and understandable

    Eloquent JS (

  • Great for solidifying intermediate

  • This is when you begin to learn "real" coding

  • Can be difficult to grasp, but with a solid understanding of the fundamentals, you should be good

    Secrets of a JS Ninja (

  • Great for going from intermediate to advanced

  • If you've methodically mastered the previous two, you will be good. Really deepens your understanding and sharpens skillset

    Finally, if you supplement all this with Codewars ( , allows you a bunch of puzzles/katas to check your level as you progress; great because you can go back and see how your skills have actually improved, you'll definitely cringe at some of your old code, ha), it's a pretty fucking awesome roadmap to get you from 0 to advanced, though like most things it'll take a lot of work.

    I've also heard good things about Free Code Camp, though I've only checked it out briefly.

    Hit me up if you have questions, always down to help others get started.
u/jellatin · 4 pointsr/javascript

This is kind of a side-answer, but it looks like you are just compiling a list of things that are super popular at the moment.

> React.js with Flux seems more hot than all other frameworks

What concerns me is that you seem to not be concerned with what is the best framework for your project(s), but rather what is "hot".

For a long-term career I would recommend focusing on improving your understanding of concepts and theory that these ever-changing tools are built on rather than trying to chase what people think is cool.

The people who spent time learning JavaScript rather than simply "mastering" jQuery were in a significantly better position when client-side frameworks came out because they knew the underlying concepts.

If you haven't mastered these things yet, I think they have more value than most of the list of specific tools I see listed:

u/user24 · 6 pointsr/javascript

Yeah JS:TGP is really required reading for professional Javascripters. I've also heard great reviews of Javascript patterns by Stoyan Stefanov. The sample chapter is good, I'm hoping to buy it later.

Felix's Node Style Guide is good too (basic style guide) and has some good rules to apply to your normal JS as well as NodeJS.

After that, browse through

Learn the module pattern and it's prettier sister the revealing module pattern and understand how it works. I use RVM everywhere by default, pretty much.

Once you've done all the above you should be able to say confidently:

  • I understand event driven programming
  • I understand scope
  • I understand closure
  • I understand prototypes

    More generally;

  • I understand the importance of separation of concerns
  • I can choose the appropriate level of abstraction for my objects
  • My code is written with re-use in mind

    General tips:

    Install firebug, JSONView. Get a good editor; I've had good experiences with textpad (win), Komodo(mac) and sublimetext(x-platform). Worry more about readability and maintainability than performance in general.

    A nice phrase I came up with the other day: Simple code doing clever things is great, clever code doing simple things is bad.

    Read other people's code. Read the unminified jQuery source, and other libraries. Try writing pure JS before going down the heavy-reliance-on-jQuery route.
u/yoqu · 2 pointsr/javascript

>At first I searched for a good guide for an average programmer, I found the [1] MDN JS Guide which is good, but I think not very good: At first I wasn't sure what is part of the language itself and what is only available at the HTML-DOM (they use a lot alert-dialogs - JS hasn't a Standard Library like Python or Java, has it?).

They use a lot of alert because it's the easiest possibility to show something for starters, you can however of course use console.log, console.warn and error. For the HTML DOM thing, well c'mon - at least try that examples in your console, will you? Just press [F12] or google for how to open the JS console for your browser.

>Is there a "JS Bible"? I know there is the tutorial for python ([2] click me) and as well there is the book/bible/reference for C (from dennis ritchie) and C++ (from Stroustrup). Does something like that exists for JS?

JavaScript: The Good Parts by Douglas Crockford

>Second Question: For my purposes, it is worth to use a Framework like jQuery? I'm using it right now, but I think it's not a big deal to code everything without using an 3rd-party framework.

I like to be able to swim, before I learn to drive a boat - and you? :)
Anyways, that depends - if you do this for clients, use jQuery, it's tested, on multiple browser, sure it has bugs, and plug ins should be reviewed by you before being used. jQuery helps to code less though, and has plenty of beginner questions already answered - just use it.

> Last Question: Atm I'm using Django as webframework and i'm very happy with it. But it looks like Node.js got lots of attention in the last couple of month, is mature enough to use it for real world problems?

It's "mature" enough yeah, but use what you need - not what is all the rage right now.

u/TehUberAdmin · 8 pointsr/javascript

But for the love of God, please, please, learn JavaScript itself to a good standard before even touching jQuery.

Even though jQuery makes writing web apps a lot easier and saves you a lot of development time, it is still a JavaScript library and as such, if you don't have a good grasp of JavaScript, you're going to be writing jQuery code that may well work correctly, but you're not going to have any idea why it works correctly and as such, debugging and writing advanced jQuery code is going to be a nightmare.

I appreciate that you might not want to spend any money on learning JavaScript, but if you're really interested in the language and want to know it well (and you already have a solid foundation in programming), then I highly recommend getting JavaScript: The Good Parts and reading through that. It's short (176 pages), you can read it in an afternoon (though the first time round, some of the stuff might go over your head), and although it may be very opinionated, most of what Crockford says is pure gold and at the end of it you will have a thorough understanding of how JavaScript works and how you can write good JavaScript, which will aid you tremendously when you start using libraries such as jQuery.

Apologies for my rantiness, it's just that JavaScript is seen as a 'toy' language by many, a simple language that people can just jump in and use without learning it first, as evidenced by people suggesting diving straight into jQuery, which is a reputation that I think is undeserved. JavaScript may not be the prettiest of languages, but it's here to stay, and if you learn to use it properly, you'll find that beneath the design mistakes lies a simple and beautiful programming language that just wants to be loved.

u/chachinsky · 1 pointr/javascript

If you associate test-driven development (TDD) with learning better code design, it might help fill in any gaps you feel you have. Best to have an understanding of SOLID principles, DRY, and KISS.

Red Green refactor is a good starting point.

Though its not JS specific, anything by Sandi Metz is awesome, highly recommend her 99 Bottles book.

Uncle Bob's Clean code is a great resource as well.

u/OriginalSyn · 7 pointsr/javascript


u/achen2345 · 1 pointr/javascript

Personally, I find I learn best from books but only for two narrow facets: theory and reference.

The books everybody recommends are:

  • Eloquent JavaScript -
  • JavaScript: The Good Parts -

    That first one can be read online.

    Once you get past the how do I write code basic literacy stuff and really want to step up into architecture you might want to get a little bit of Lisp and Scheme. The fundamental concept to learn in this language is scope. In my experience computer science grads tend to learn things like C++ and Java or C# and work really hard to get really good at OOP. Those techniques of inheritance aren't quite so helpful in this language if you never learn this language's scope model. If you fall in love with the scope model you might find you don't need the OOP/inheritance stuff.

    When you are ready to interact with the web here is a quick guide I wrote to teach DOM access: Could you let me know where this guide fails you so that I can improve it for other people?
u/webdevrr · 6 pointsr/javascript

First, make sure that you've built some complex apps in vanilla JS, and have faced some sort of issue of scale (ie. problems that came up because your app has a lot of code). Maybe your code is really long and difficult to organize. Maybe you end up repeating the same code in a lot of places. Etc.

That way when you try a framework, you'll have some idea why it does what it does, and what problem it's trying to solve.

As far as specific libraries, I'd try these in this order:

u/noman_land · 2 pointsr/javascript

Take a look at the book Effective Javascript. It's a really excellent book that deep dives into specific examples and what to look out for.

Secondly, check out some of the tutorials on They get into some really neat and important Javascript things.

Thirdly, write some backend Javascript code in nodejs so you can use the skills you already have but apply them to backend concepts. Heroku has some really nice tutorials that will get you writing server code in just a few minutes.

Fourthly, use one or more of the popular frontend frameworks to build a simple Todo app. In fact, if you have the time, build the same Todo app in a few different frameworks, so you get an idea of how they work.

Also, when interviewing, just be honest. Tell them you have a number of years of experience but that you've worked for organizations that preferred quick and dirty over perfect. You can parlay that into a positive by showing how learned to get stuff done quickly without spending too much time on small details.

u/eddyvanhelgen · 1 pointr/javascript

Books that helped me to get the hang of JS

John Resig's Secrets of the JavaScript Ninja and Douglas Crockford's JavaScript: The Good Parts are pretty much the only ones worth reading in my opinion.


The best thing would be to build something you want to use yourself. Maybe you try cordova and build a small app with the browser platform so that you can create a simple App that you can bring to your Smartphone.

More advise

Read a lot of code: TODO MVC is a good place to start, people try to write good code for this one because they want you to use their framework :-). The problem with the source code of many projects is that the JS ecosystem is in a constant flux and ES6 modules are skyrocketing right now. You may want to check out the jQuery source code - you can pretty much watch the evolution by looking at older versions of the source code and how it evolved.

If you feel really adventurous the NodeJS source code is a fun read - although it's a very big project that also got some C/C++ code sprinkled in - but that shouldn't be a problem for you :-).

I would advise you not to bother reading the Angular1 code for the time being, Angular2 maybe interesting but its written in Microsoft's TypeScript - which is a nice language on top of JS that is worth learning about.

u/pacificano_au · 2 pointsr/javascript

For Javascript, I recommend "A Smarter Way to Learn Javascript"

It's a really good, QUICK, and straight to the point book on beginner Javascript. ~250pages

Then... If you want to round it out, I'd recommend Head First Javascript Programming While being full of fluff, as is Head Firsts way, is a much better book than their HTML5/JS one. With a lot of great examples ~600pages

After that, I'd recommend Learning Web App Development ~300pages which will start to introduce the full javascript stack to you.

u/theQuandary · 3 pointsr/javascript

Javascript: the good parts -- Amazon

Eloquent Javascript -- free ebook

Javascript Allonge -- free ebook

Eloquent Javascript is a great introduction to JS. The Good Parts teaches about what parts of JS to use and good coding practices (though some JS devs disagree with Crockford, every place I've worked that started implementing all his recommendations immediately saw reductions in code issues). Javascript Allonge is the greatest intro to functional JS that I've seen. These three will take you from beginner JS dev to intermediate JS dev. Practice will take you to advanced JS dev and reading lots of nuts and bolts blog posts will take you to JS expert.

u/spencercooley · 1 pointr/javascript

I am self taught and I have to say that the best way to learn is to have a very clear idea of a simple project that you can realistically complete. I learned javascript with "JavaScript: the good parts", and I built a page with a deck of cards that shuffled when you press a button. I still have it on github

Both books you mentioned are probably good, but the real learning happens when you are trying to accomplish a specific goal and get stuck on something.

"Javascript the Good Parts" is definitely good, very light and to the point.

u/noprompt · 2 pointsr/javascript

In addition to the others mentioned, these are also well worth your time:

Eloquent JavaScript

JavaScrip: The Good Parts (This one is essential)

As far as functional programming goes, google "functional programming in javascript." There are several articles on the subject and you'll learn some very useful and interesting techniques. Using a functional style in JavaScript can be extremely rewarding and not to mention a lot of fun!

u/StoneCypher · -2 pointsr/javascript

Everyone here is going to give you a bunch of 30-days or head-first books - many of which will have the ostensible impremateur of big names like Crockford and Resig.

Let me be the first to tell you to basically ignore this crap.

Read the standard, get a good reference on browser differences, then focus on real programming books that are not language specific. That's the way to rise above making jQuery plugins and "HTML5 Game Demos" of Atari 2600 games.

The standard:

Good reference on browser differences:

The kinds of books you should be reading (notice the used prices please):

I'd throw in a rickroll if I could.

A deep knowledge of CSS will help. If Javascript is your hammer, CSS is your screwdriver; the two are very related in most cases (sure there are exceptions, like node servers, but they're not common.)

Like JS, the best way to learn CSS is the standard.

Happy hunting.

u/michaelp983 · 3 pointsr/javascript

I feel like this is a classic book for javascript programming. Even though it is very opinionated (parseInt), but none the less it is a great reference for quirky behavior of JS. Seconde watch this: <-- Just a great list of really silly behavior of JS!

One last thing, make sure you review how CommonJS works:

u/zzgzzpop · 2 pointsr/javascript

If you're picking up JavaScript as a first language, it might be a bit difficult. It's used so often for the web that you'll most likely be required to learn at least some HTML and CSS as well. But, if you're not discouraged by this there's a lot of resources out there.

The one stop shop that'll give you everything is MDN ( Which has pretty much everything you'll need about JavaScript (

If you don't know anything about HTML or CSS you might want to at least go through the introductions before jumping over to JavaScript:

As for programs to use, to start, all you really need is a text editor (I recommend and a browser. If you're using Chrome press F12 and that should bring up the developer console and type:

console.log("It is " + Date());

Congrats you just wrote JavaScript.

Once you feel more comfortable you'll definitely want to pick up JavaScript: The Good Parts (

u/nvdnadj92 · 1 pointr/javascript

Just to throw in my two cents here, I learned how to think in terms of "clean code" after watching a set of lectures by Robert C. Martin, AKA uncle Bob. He provides an conceptual framework for how to write "clean code" and is widely accepted as the subject matter expert in the software engineering community.

I highly recommend it -- He goes over things like "how to name variables", "when to split up functions into smaller ones", "how to structure programs", etc. I'm not kidding when I say that those lectures were the most meaningful improvement I have made as an engineer.

He also has a book too!

u/RecycledAir · 6 pointsr/javascript

I've recently been working on my JS skills and heres a few resources I've found super useful:


Javascript Patterns

Javascript: The Good Parts

Javascript: The Definitive Guide (While an exhausive resource on the topic, this one is a bit verbose)


Mozilla's Javascript Guide (One of the best free online javascript guides/references.

How to Node (Tutorials on server-side Node.js)

Daily JS (Interesting JS related news)

Echo JS (Similar to above but updates less frequently)

Hacker News (This is more general tech news but there is a ton of useful web stuff, especially as node.js is currently a hot topic. Reddit actually spawned from HN)

Online Videos (free)

Douglas Crockford's Javascript Lectures (I would recommend these to anyone getting into javascript)

u/ginzer · 1 pointr/javascript

I come from the same background. Lot's of good recommendations here. I read this book:, watched a video series version of Crockford's "Good Parts", and went through this Udacity course: Hope that helps. Good luck!

u/BadRandolf · 1 pointr/javascript

I'd go for method 3, though I'd write the functions differently (ex. currying a function that can return undefined is not a good idea). I'm talking about the overall approach here.

My reasoning (and some of this is subjective I know):

  • If this isn't being called hundreds of times a second then performance takes a backseat to readability, maintainability and re-usability. I'll gladly sacrifice a few cycles per second to improve any of those things. Of course none of those are mutually exclusive, you can rewrite the code in Method 3 to be a lot faster than what's written in the OP without losing any readability.

  • Each function is short, has a descriptive name and is easy to understand at a glance. When you're working alone maybe this isn't so important, but when you're working on code with 10 other people contributing it makes the whole process much easier. See Clean Code

  • You can easily reuse parts of the algorithm in Method 3 (eg. isShortMessage could be part of an if statement somewhere). The other 2 methods solve one problem and one problem only. If you suddenly find you need a function like isShortMessage somewhere you're either left duplicating code or rewriting those functions to make them more generic.

  • Method 3 is easier to debug. This is a pretty minor point and it's somewhat nullified by the function currying at the end, but it's something to think about.
u/porlov · 2 pointsr/javascript

> But co-writing with a book takes up a lot more time than co-writing with video.

If by co-writing you mean writing the examples from the book/video and making them work, well I never do that. I always read technical programming books as fiction and never try the examples. Sometimes I just return to particular parts in the books for reference, but that's it. For the practical part I do my own things. I don't have time to retype the examples from the books, my life is too short. I got plenty of needs that imply writing software to solve my own personal practical problems. If I think about it long enough, I always come up with some really small project that's (at least theoretically) possible to be made by an almost complete language newbie.

I don't know how useful my personal experience would prove to you, but here you go. My JavaScript journey started when I was living in a cave with no internet access and a very old computer with such a small amount of RAM that it could only run Opera. I found three books about JS on some old CD and picked the basics from them. Having a bit of prior programming experience helped, but I wouldn't overestimate that influence.

Here are the books:

I found the first one most interesting and useful, the last one was good to use as reference and replacement for the lacking access to online searches.

As you can see, all of them are quite old (and maybe outdated already, since the JS ecosystem moves ahead so fast).

I'm pretty sure there are tons of newer books nowadays.

Very recently I was suggested to have a look at but I didn't manage to get some time to have a closer look at it, so I can't comment on the content there.


u/ridicalis · 18 pointsr/javascript

The first thing that comes to mind is understanding scope. In particular, if you come from a C-esque language, this might be one of your biggest hangups. Understanding how the scope works before you write your code will inevitably lead to a better-written product.

(tl;dr for the rest of this: know the fundamentals)

The route I came up, I started as an OOP developer and thought JS was a toy language for much of my career. It wasn't until I took the time to understand the language that I came into my own as a JS dev, and it is currently my favorite language to develop for. If you're the book-reading sort, I would suggest the following resources in sequence:

  • JavaScript: The Definitive Guide (David Flanagan)
  • JavaScript: The Good Parts (Douglas Crockford)
  • JavaScript Patterns: Build Better Applications with Coding and Design Patterns (Stoyan Stefanov)

    If you follow this link and look at the Frequently Bought Together section, you'll see that these three form a common trifecta. What you can expect:

  • The first book will give you a fundamental understanding of the language (I would personally skip the DOM-related parts, since that's more framework/environment than language)
  • The second book will tell you "Okay, we just gave you a drawer full of knives, here are the ones that won't send you to the hospital"
  • The third book gives you a rationale for how and why to apply the language in certain ways. It deals with JS-specific issues, and also brings in some of the Gang of Four patterns and other best practices.

    (edit: added link to Amazon page for the first of the three books, fixed formatting)
u/emkay · 1 pointr/javascript

I agree that is a pretty good read for a beginner to go through.

In there he uses this pattern, (function(){})() which is very powerful and useful. He is however using what Crockford calls, "The dogballs pattern", and suggests that you do this instead


although that seems to be a minor style point. I would also recommend reading js patterns and the book Javascript Patterns, this is of course after a more in depth review of The Good Parts. There is some really good stuff on YUI Theatre. It isn't just about YUI, and has some really great talks and lectures. Also you don't have to join an open source project, but you do have to keep hacking. I would recommend you to get a github account and start working on some basic js demos to show off. Then maybe come back and make a post here with the link and ask some people to review your code. You can learn a lot by making mistakes and people telling you. PM me if you want me to look over anything.

u/rjett · 6 pointsr/javascript



Old, but probably still relevant

Yet to be released, but you can get the in progress pdf from the publisher


The one that everybody recommends

HTML5 spec


Latest Webkit News

Other than that build build build. Make demos and play. Ask questions here or on stackoverflow and read other people's code. Also, lots of great old JSConf videos out there.

u/nikoskatsos101 · 1 pointr/javascript

Start here , but don't forget to check

The first one will help you to get started and the second one will help you to build a strong base on what's happening and why.

u/mrskitch · 2 pointsr/javascript

JavaScript is no longer considered a "toy language" and is become much more relevant and demanded due to server platforms that run it (node.js being the biggie).

You should really familiarize yourself with what's happening in the JS scene. To start, take a look at:

  • Bower
  • Grunt
  • Nodejs obviously

    If you're gearing towards UI:

  • Angular
  • Backbone
  • Ember

    Also, read:

  • Eloquent JavaScript
  • The Good Parts
  • Functional JavaScript

    I was never a Java developer, but was a PHP developer back in the day. Things like NPM and Node (for building, or writing back-ends) have made my life a hell of a lot easier and less "hackier". You can primarily concern yourself with just integration/work code instead of busy stuff, like copying crap over or adding another lib to your VCS system. Just add it as a dependency and you're off and going.

    That being said, JavaScript is really hard to get good at. There is no "standard" way of doing anything, and everything has it's benefits and drawbacks. You need to know which is better and why, and when to break the rules. It's quirks can be tool for powerful code, but you need to know why it is that way.

    If you think I'm joking, take a look at this rant.
u/OrneryFellow · 2 pointsr/javascript

I started out with going through the book Javascript: The Good Parts. It's fairly straight to the point and goes over the parts of Javascript that differs from other classical OOP languages pretty well. As the book title suggests, it doesn't go over everything in Javascript, but only the practical parts. Great short read.

u/rodion_89 · -5 pointsr/javascript

Don't listen to jakelear, w3schools is an excellent resource for beginners.

That said, once you are on your feet and getting deeper into JavaScript check out these books. They are wonderfully useful and informative.

u/pdoherty926 · 1 pointr/javascript

Start with Beginning JavaScript with DOM scripting and Ajax: from novice to professional (pretty old skewl, but a it's a great intro and is library agnostic) and then move onto Eloquent JavaScript, The Good Parts and Pro JavaScript Design Patterns.

u/AceBacker · 1 pointr/javascript

All I care about is clean code. Code that is easy to read and change. If a framework helps you do this fine.

If you haven't heard of Uncle Bob check this out:

Or if you prefer his goofy video's:

u/guitarino · 2 pointsr/javascript

I really recommend a book Clean Code by Robert C. Martin. It can really help you understand how to write clean code, which you can use and improve right away.

u/sharkmandan · 1 pointr/javascript

For more advanced topics, "Secrets of the JavaScript Ninja" covers many of the advanced techniques popular libraries use (including prototype and jQuery), written by the jQuery creator.

It assumes you have an understanding of the fundamentals so it gets into the advanced topics pretty quickly.

u/Gacnt · 1 pointr/javascript

Javascript: The Good Parts

Javascript: The Definitive Guide

I use the Definitive guide as a reference book, but if you have the patience and want to learn, definitely a good read.

u/automathematics · 1 pointr/javascript

Highly agree. Buy a kindle and read anything people you trust recommend.

I would recommend one javascript specific book, actually:

I've been doing this a long time and there's still some stuff in there for me to learn every time I flip through it.

u/ScopeChain · 1 pointr/javascript

no problem, i strongly recommend that your read javascript the good parts by Douglas Crockford who is considered the god of javascript, it's a short read which will clear a lot of confusion and teach you what a powerful and nice language js is

u/fjaxyu · 1 pointr/javascript

There are a ton of online resources for learning JavaScript. has sales on their courses often, but even YouTube has a lot of good tutorials. But I really enjoyed reading this book: JavaScript and JQuery: Interactive Front-End Web Development

u/hhustlin · 3 pointsr/javascript

Just out of curiosity, what's the perceived benefit of logging every page in your history as a QR code of all things?

As for language - Chrome extensions are JavaScript, so if that's what you want to do, learn that. If you're looking for the very basics, Codecadamy is a good place to start. Beyond that, you're on your own (but maybe pick up a copy of the Good Parts )

u/goldfire · 38 pointsr/javascript

The bottom line is that, whatever your rationale might be, this code is extremely difficult to read and understand for anyone who isn't you. I had to just skip over the entire tokenizer because I wasn't getting anything out of trying to read it, except for frustration. The algorithm portion isn't much better.

Good names are one of the best ways for an author to communicate how their code works to other programmers. They provide the foothold that the person reading the code needs so that they can begin understanding the algorithms. With what you've got here, the reader must already understand the algorithms before ever seeing the code, so that he can map the concepts he already has in his head onto the uninformative variable names.

I'll give you an example that I paraphrased from Code Complete, which, if you haven't heard of it, is one of the absolute classic works on the topic of how to construct good code. What do you think this code fragment is doing:

a = a - b;
c = d + sales_tax(d);
a = a + late_fee(e, a) + c;
a = a + interest(e, a);

Despite the good function names, it's still extremely difficult to figure out what this code is trying to accomplish; if I have to make a change in something that relates to this module, I don't know where to start. But, after we name the variables:

balance = balance - last_payment;
monthly_total = new_purchases + sales_tax(new_purchases);
balance = balance + late_fee(customer_number, balance) + monthly_total;
balance = balance + interest(customer_number, balance);

See how much easier it is now to see that this code is computing a customer's bill based on their outstanding balance and a set of new purchases from the current month?

Using good variable names allows anyone to just read your code and understand immediately what it is doing. Without good variable names, anyone reading your code has to already know what it is doing.

u/whobutsb · 2 pointsr/javascript

Get your hands on Douglas Crockford's book "Javascript the Good Parts" (
That will help you get started with the language.

Here is a talk he did at Google:

If your looking for some neat boundary pushing javascript check out the site:

u/RankFoundry · 2 pointsr/javascript

If you check out the first chapter on Amazon, the author says that's exactly why and who he wrote it for. He explains how to get the same OO features you're used to out of JS but also how to utilize the unique aspects of JS:

Hope it helps. It helped me out quite a bit as I transitioned towards more front-end work

u/simonsarris · 14 pointsr/javascript

Read JavaScript: The Good Parts by Crockford. He goes over structuring JavaScript in an OOP fashion. More generally it's a great book that will bring your understanding of JS from intermediate to the beginnings of expert.

u/ThatsRightBud · 1 pointr/javascript

I was actually reading JavaScript Patterns before vither999 recommended the book he did. So i'll definitely check out the book you're suggesting too! Thanks!

u/w3cj · 5 pointsr/javascript

I highly recommend checking out the You Don't Know JS book series by Kyle Simpson. It goes in depth into how the language works and all the quirks you might encounter:

If you'd like a shorter read and maybe have your opinions formed for you... checkout JavaScript the good parts:

u/alexlafroscia · 1 pointr/javascript

I always recommend Secrets of a JavaScript Ninja, which has been a great tool for me to learn some of the intermediate to advanced JS stuff. Covers some basics too, but is mostly for learning the deeper stuff. I like it a lot.

u/Sancty · 9 pointsr/javascript

Clean code... you can find it on amazon or anywhere else. Pretty highly regarded.


u/MahmudAdam · 1 pointr/javascript

I know you specified PDF books, but this one gets pretty good reviews: I believe the book assumes no prior programming experience. You could also go through the JavaScript course on

u/zach_will · 0 pointsr/javascript

MDN Doc Center (or MDC) is indispensable.

If you're looking for a solid book to learn it quick, Stoyan's Object-Oriented JavaScript or Nicholas Zakas' Professional JavaScript are the easiest to read and hit the ground running (as opposed to Crockford's book).

I actually learned quite a bit from Crockford's older talks on YUI Theater — scroll around halfway down the page for his Advanced Javascript and The Javascript Programming Language talks.

Also, word of advice, JavaScript itself is really easy to pick up — especially if you've programmed before. The thing that is going to cause you the most trouble is interacting with the DOM (and browser quirks, etc). There are multiple libraries to help you out, and, while everyone has their own preference of which to learn, jQuery is probably your best bet. I'm not saying it's better than the others, but you will need to know it if you apply to front-end developer jobs.

Lastly, if you are willing to pay money, I really feel you can't go wrong with Stoyan's book.

u/Chesh · 3 pointsr/javascript

It's a design mistake in the language itself, there are quite a few of them. I recommend Douglas Crockford's JavaScript: The Good Parts, he goes into a lot of good practice work-arounds for the pitfalls of the language.

u/Demon1 · 1 pointr/javascript

i recently purchased JavaScript Patterns by Stoyan Stefanov and i'm quite satisfied with it. You should check it out too, think it will help you. Although author says it's not a beginner book, I think a person knowledgeable in other programming language(s) could make use of it.

u/sundried_tomatoes · 1 pointr/javascript

my friend vows by the head first series. I never liked it, but might be good for beginners.

u/iTipTurtles · 2 pointsr/javascript

JavaScript & JQuery: Interactive Front-end Web Development I have been working through this and its quite good. Well structured and designed, so it isnt just a wall of text.

u/molant · 5 pointsr/javascript code complete. One of the best books about coding in general that I've ever read.

u/saturdayplace · 2 pointsr/javascript

I haven't got more that a handful of chapters in, but so far I really like Professional JavaScript for Web Developers

u/[deleted] · 1 pointr/javascript

I think I finally understood this by using it a whole lot to find out how it worked, rather than reading any specific resource.

I recommend Professional Javascript for Web Developers by Nicholas Zakas.

Also check out Addy Osmani's blog, especially his piece on Javascript Patterns.

Would I hire you? If I was in a position to do so, sure! But I'm a contractor ;)

u/TJSomething · 2 pointsr/javascript

I would like to add JavaScript Patterns, which has several ways to structure your code like this.

u/SoftwareEngineur · 2 pointsr/javascript

You're probably going to get a myriad of reactions to this question, but usually the consensus is usually JavaScript: The Good Parts

u/planetstarbucks · 7 pointsr/javascript

Buy Clean Code ( This book is my bible. Read it through once quickly, and refer back to it once in awhile, and I can guarantee you'll never write spaghetti code again.

u/codaboom · 1 pointr/javascript

This was an excellent book. Very thorough and got me learning my first few months of JS

u/magenta_placenta · 0 pointsr/javascript

How much raw JavaScript is it worth knowing? All of it.

Also keep in mind that JavaScript, while object-oriented, is a prototype based language (there are no classes like Java). You can emulate classes in JS using functions as constructors, but there are no classes (even though "class" is a reserved word in JS).

I really recommend these JS books (before jQuery):

JavaScript, The Definitive guide

Pro JavaScript Design Patterns

JavaScript Patterns

u/dallaylaen · 2 pointsr/javascript

This may sound old fashioned, but maybe this classical book "Introduction to Algorithms" by Cormen et al is the way to go.

I myself learned by another book, "Algorithms and Programming: Problems and Solutions" by Alexander Shen, which was way thinner. Just read it through and solved like 50% of the exercises in C, Java, or Perl.

u/notThaLochNessMonsta · 2 pointsr/javascript

There are more than 356 people in the programming community. This isn't Mumps.

I agree most of the time that early returns are better. But this isn't proof that "most of the programming community agrees". You realize that there is a substantial amount of developers who believe in only 1 return per function, right? Something that is evangelized in Clean Code.

u/voidpirate · 2 pointsr/javascript

I would check out Secrets of the JavaScript Ninja

It's a great book if you are coming from a different programming language to JavaScript. The syntax of JavaScript may feel familiar but don't be fooled. Javascript has many different quirks, that you should wrap your head around in order to write "good" JavaScript.

u/areinet · 3 pointsr/javascript

My suggestion, go read Crockford's book JavaScript: The Good Parts and/or the JavaScript section of his blog. A lot of people have some really strong opinions on whether Crockford is right or not, but simply reading his book will explode your JS knowledge in a big way. Its a quick read and then you can start having your own opinions on Crockford.

Also, as someone else posted here, go build something.

u/Dwaligon · 2 pointsr/javascript

Just read Jon Duckett's new Javascript book and this was a good gauge for how much I learned. Thanks!

u/BruceJillis · 2 pointsr/javascript

The Pragmatic Programmer. Here is a quick ref that gives a good overview of the contents.

u/jreborn · 3 pointsr/javascript

The C Programming Language is a good one too. Although it's specific to learning C, reading through it and doing all the exercises is something every programmer should do at least once.

Also, Code Complete 2.

u/georgegkas · 1 pointr/javascript

There are people who believe JavaScript does not favor good programming styles (I do not support that statement). In my university this semester, a group of graduate students presented a 12-hour course in Python. In many cases, they compared the language with other scripting ones, such as JavaScript, with not so friendly remarks about the language itself and its ecosystem in general. I can understand this claim: JavaScript was created to favor simplicity. Back in 90s, the WWW was still young. Eventually, there was a need to add interactivity to Web Pages. There were many choices, but all of those possible solutions had a stiff learning curve. JavaScript was introduced as a simple scripting language for the web that would target non-developers (there was not such thing as web developers in mid 90s). Unfortunately, the standardization process of the young language (ECMAScript) was not organized with every major browser implement different set of its features (hello IE!). There were not such thing as Design Patterns for JavaScript (until someone introduced them in the wide audience). Years, passed, the Internet evolved, so did the language. There are many things to like about JS today, but this is out of scope of this post. I cannot find a single point of reference about this debate, there are discussions all over the Internet. If your goal is to write a post about this debate, then you have to search for the main arguments of "JS haters" and "JS lovers" manually. Also you have to understand where the term "programmers" refer to. Who is your reference? The Senior developer at a big company, a Junior one, random people that do not know the real aspects of programming, etc. Then you can start researching about the different opinions. Feel free to update your post if like to, but answering "Why people in general hate JS" is quite ambiguous.

u/jimbol · 1 pointr/javascript

I try not to use square brackets when I'm not doing a variable lookup.
With $_GET['distro'] the string 'distro' never changes. So you can just use dot notation.$_GET.distro and cut out some characters.

Also if you're going to run a look up more than one, consider storing the results in a variable. For example you do distro[$_GET['distro']] a couple times. Instead store the result var distroValue = distro[params.distro]

This is especially important with jquery lookups like this $('#inner') because its a really heavy operation to execute a DOM lookup. Instead store the results of the lookup for later use. var $inner = $('#inner');

Heres an annotated version of your code with my notes.

Heres a more readable version of you code.

Also read Clean Code.

u/robdelorean · 1 pointr/javascript

It's a little dated now but surprised Javascript for Web Developers by Nicholas Zakas isn't on there.

u/Doctuh · 3 pointsr/javascript

Crockford, then Effective Javascript, then the Resig above, then you branch out into your interests.

u/PhishGreenLantern · 1 pointr/javascript

A quick google search will turn up a PDF of it. I'm almost certain that it's a legit, free copy, but I'm not positive. You can get a used, physical copy for $9:

u/underwatr_cheestrain · 34 pointsr/javascript

Get your man pants on and pick up a copy of CLRS.

u/Chronic8888 · 1 pointr/javascript

On this front... do everything you can on node school and on a somewhat unrelated note buy/download this book

u/deathbysniper · 2 pointsr/javascript

My coworkers and I have been slowly going through this book for a while now and we've all learned a lot.

u/GoldenRetrieva · 1 pointr/javascript

I think its called HTML5 but there is a big emphasis on javascript

edit: theres actually one just for javascript but i've never read that one

u/takethemoneyrun · 1 pointr/javascript

What really helped me get my head around js and oop was Resig's book

For day-to-day issues and stuff I also use, especially their Javascript Reference

u/Mob_Of_One · -4 pointsr/javascript

This book will save you MANY hours of pain.

JavaScript is not OO.

Good JavaScript is not imperative.

Good code period doesn't rely on mutating globals.

u/duxdude418 · 2 pointsr/javascript

[JavaScript Design Patterns] ( by Stoyan Stefanov. Covers more than just design patterns in a traditional sense, but JS patterns of all kind, highlighting and explaining syntax one might not be familiar with along the way.

Call me a heretic, but I found ...The Good Parts to be lacking. While most of the advice is sound, readers are expected to take it as gospel without much explanation. Patterns shown also lack concise implementation examples, and the ones that do tend to rely on utility methods developed in earlier chapters, making it more difficult to use as a reference.

u/borscht · 1 pointr/javascript

Are you being a dick? Or do you just have a weird way of asking genuine questions? It's not a joke, manual memory management has nothing to do with algorithms or data structures. Intro to Algorithms by Cormen is a famous book used by a lot of universities with top computer science programs and all of the examples in the book are written in a garbage-collected pseudo-language. A proper algorithms & data structures course focuses on the mathematical foundation that algorithms & data structures are built upon. Worrying about allocating and freeing memory is a distracting implementation detail that adds no value to the course.