Oh, I can name you a few times it's worth using bind. Currying, for instance. But you should avoid bind unless you need it. Simply using it to permanently set scope is not a good usage; use an anonymous call (apparently not apply!!) for that.
It is strange that apply is slow; I would think that would be optimized better than call.
function sub_curry(fn /*, variable number of args */) {
var args = [].slice.call(arguments, 1);
return function () {
return fn.apply(this, args.concat(toArray(arguments)));
};
}
It completely agree it is definitely worth using bind to ensure that this is commonly understood and doesn't get lost. If you don't use this, though, you don't need bind.
4
u/oefig Mar 09 '15
Could you explain further in what ways bind/call/apply can affect performance? I love using
bindto set up my handler functions like so:... over:
I always thought
.bindand.applyfit well into Javascript, but if I shouldn't be using them please tell me why!