Home » Javascript » JavaScript bind() for cleaner code

JavaScript bind() for cleaner code

Several weeks ago, I wrote about how closures impact calling asynchronous functions in a loop and several ways of dealing with that problem.

In my recent coding, I’ve discovered an even more simple way of dealing with this problem. In the process, it removes the anonymous function and eliminates the linting error, ‘Don’t make functions within a loop’

You see, I’ve been experimenting with JavaScript bind(). And as it turns out, we can use bind in multiple situations, including dealing with the closure issue I mentioned a couple of weeks ago.

JavaScript bind() for cleaner code
Photo credit: Connor Tarter via VisualHunt / CC BY-SA

What Is bind()?

The bind function is a recent addition to the JavaScript spec. So this will only work on recent browsers. You can check the compatibility table (for all things JavaScript) to see which browser implement bind() as well as other JavaScript features. I looked over the list and there aren’t any browsers that don’t support bind() that I care to support, so I’m good. Your mileage may vary.

What bind does is that it automatically wraps your function in its own closure so that we can bind the context (the this keyword) and a list of parameters to the original function.

What you end up with is another function pointer.

Notice that we not only bound this to the foo() function, but we also bound the two parameters. So, when we call newFoo() the return value will be 7.

But what happens if we change the parameters before calling newFoo?

Changing bind parameters

If we bind parameters to foo() using variables and then change the variables prior to calling newFoo(), what do you expect the value to be?

The return value is still going to be 7 because bind() binds the value of the parameters, not the actual variables.

This is good news and, like I said, we can use this to great advantage in our code. But where I think it will display the most usefulness to me is in my call backs

Bind and callbacks

You should remember from that article that one of our solutions to dealing with callbacks in loops was to create an anonymous function around the function we wanted to call.

But we can greatly simplify this code by using bind instead.

We can do this because each call to bind gives us a new function pointer and the original function remains unchanged.

Meanwhile, we also remove the linting error ‘Don’t make functions within a loop’ because we aren’t creating the function in a loop, we are just pointing to a function that was created outside of the loop.

Bind for Event Handlers

Another place where bind() will clean up your code is with event handlers.  Everyone knows, or should know, that when an event handler is called, the context it is called on is the thing that generated the event and not the object that the event handler was created in.  But, by using bind, you can be sure that the function is being called on the correct context.

Not that you would write your code exactly like that, but that is just to get the point across.



OK.  I’ll be the first to admit that my functional programming knowledge is limited.  But the best definition of Currying I can give you is that it allows you to pass parameters to function in multiple steps.

Using binding, we achieve Currying by writing code that looks something like this:


Other post in Javascript
JavaScript bind() for cleaner code
Article Name
JavaScript bind() for cleaner code
Here are multiple ways you can use the JavaScript bind() function to create cleaner, more maintainable code.
DMB Consulting, LLC

About Dave Bush

Dave Bush is a Full Stack ASP.NET developer focusing on ASP.NET, C#, Node.js, JavaScript, HTML, CSS, BootStrap, and Angular.JS. Does your team need additional help in any of the above? Contact Dave today.

Leave a Reply

5 Comments on "JavaScript bind() for cleaner code"

Notify of
Sort by:   newest | oldest | most voted