Why does angular.bind() exists while core javascript has the same functionality?

Question

In the angular documentation it says that you can take an object and bind it to a function with optional arguments like this:

angular.bind(self, fn, args);

If I understood correctly "self" becomes "this" for the returned (and modified) fn.

This is also easily done with core javascript:

fn.apply(obj, args);

Am I missing something here?

see http://stackoverflow.com/questions/30529933/what-is-the-use-of-angular-bind-in-angularjs-where-to-use-it — Barudar, Jan 06 '17 at 13:34

score 2 · Accepted Answer · answered Jan 06 '17 at 13:49

angular.bind creates a wrapper function with specified context. It is a counterpart of Function.prototype.bind, not Function.prototype.apply.

angular.bind is there from old days when it was good manners for JS libraries to be self-sufficient and not rely on standards and polyfills (a tribute to jQuery and jQuery.proxy). This often resulted in smaller footprint.

angular.bind and fn.apply won't work with newed ES6 classes, it is preferable to stick to fn.bind if it fits the case.

Why does angular.bind() exists while core javascript has the same functionality?

1 Answers1