Return to Answer

##Most of the time it does not matter.

##However yes, when it matters - .bind is slower

###First, let's look at the bind algorithm defined in the specification:

1. Let Target be the this value.
2. If IsCallable(Target) is false, throw a TypeError exception.
3. Let A be a new (possibly empty) internal list of all of the argument values provided after thisArg (arg1, arg2 etc), in order.

 

...

 

(21. Call the [[DefineOwnProperty]] internal method of F with arguments "arguments", PropertyDescriptor {[[Get]]: thrower, [[Set]]: thrower, [[Enumerable]]: false, [[Configurable]]: false}, and false.

 

(22. Return F.

###Second , let's see how it's implemented in Chrome.

Most of the time it does not matter.

However yes, when it matters - .bind is slower

First, let's look at the bind algorithm defined in the specification:

1. Let Target be the this value.
2. If IsCallable(Target) is false, throw a TypeError exception.
3. Let A be a new (possibly empty) internal list of all of the argument values provided after thisArg (arg1, arg2 etc), in order.

...

(21. Call the [[DefineOwnProperty]] internal method of F with arguments "arguments", PropertyDescriptor {[[Get]]: thrower, [[Set]]: thrower, [[Enumerable]]: false, [[Configurable]]: false}, and false.

(22. Return F.

Second , let's see how it's implemented in Chrome.

Chrome 59 update: As I predicted in the answer below bind is no longer slower with the new optimizing compiler

Chrome 59 update: As I predicted in the answer below bind is no longer slower with the new optimizing compiler. Here's the code with details: https://codereview.chromium.org/2916063002/

##Most of the time it does not matter.

Chrome 59 update: As I predicted in the answer below bind is no longer slower with the new optimizing compiler

##Most of the time it does not matter.