What is a Promise, and what is the difference between a Promise and a Deferred object? (in JavaScript (ES6), or jQuery)

A promise is an object.

It is an object that can tell you some value (possibly), in the future.

Besides telling you some value, it can merely tell you that some lengthy task is done.  But for now, let’s just say it is some value that we want.

It can be some value that needs to be fetched from the Internet, or it can be some complex calculation that can take a long time, and the Promise object can possibly tell you later.

It is an observable, as in the Observer Pattern.

In JavaScript that supports ES6, such as in the current latest version of Chrome browser, you can just get a promise by:

var somePromise = new Promise(function( ... ) { 
   //... 
});

The function passed to the constructor is the “worker” that will somehow get the value, for this promise object.

We say “the promise” object is obtained immediately.  That’s because the promise object is created, but the expected value or the lengthy task is not done yet.  But the promise object is created and returned to you immediately.

Now we have this promise object.  And it can be observed:

somePromise.then(function(someValue) { ... });

This is to tell the promise object: “let me know when you succeeded in getting the value (or have finished the task)”.

If you use the “catch” method:

somePromise.catch(function() { ... });

then it is to say: “let me know when you cannot keep the promise (of providing me the data or finish the task for some reason).”

Because the then() method and the catch() method both returns the very same promise object, we can chain them together:

somePromise.then(fn1).then(fn2).then(fn3).catch(handler1).catch(handler2);

or we can register the observer multiple times:

somePromise.then(fn1);
somePromise.then(fn2);

and fn1 and fn2 will be invoked in that sequence we register them, when the promise has succeeded.

Now, remember the function we pass to the Promise constructor?  That’s the worker to get the value, or to finish some lengthy task.

var somePromise = new Promise(function(resolve, reject) { ... });

The function actually takes a parameters, which is a resolve function and a reject function.

When that worker finally gets the value, or finish the task, it will say, “hey, I honor the promise”, by invoking

resolve(someKindOfValue);

or when it cannot get the promised value or finish the lengthy task, it will say, “oh I cannot keep the promise”, by invoking

reject();

I may also use the name for the “resolve” function as “honor_with”, and name the function “reject” as “not_keep”, to make it easier to visualize keeping a promise or breaking a promise.

So let’s look at an example:

http://jsfiddle.net/KennethKinLum/tvsqoo27/

Here, we create a promise object:

var promise = new Promise(function (honor_with, not_keep) {
});

Note that the promise object is instantiated and returned immediately. The function is invoked, but we should only set up or initiate the lengthy task: for example, we can start the AJAX call to fetch some data, or set up the calculation of something complicated, but we should not actually do all those calculations right at this moment.

Now, as a user of this promise, we can say:

http://jsfiddle.net/KennethKinLum/tvsqoo27/2/

promise.then(function (foo) {

    $("body").append("Person A: wow I just know that the promise was kept, with the data being " + foo + ", at " + (new Date()).toLocaleTimeString() + "</div>");

});

Note that jQuery is used, but it merely is used to display something in the document body. (In other word, the promise we are talking about is not a jQuery promise, but an ECMAScript promise).

Now, we can simulate some lengthy task, by having the worker doing something, every second:

http://jsfiddle.net/KennethKinLum/tvsqoo27/3/

setInterval(function () {
    $("body").append("Person B: I am thinking or not doing anything, at " + (new Date()).toLocaleTimeString() + "</div>"); }, 1000);

Right now, it is just not doing anything, but just adding a message to the screen, to show that it could be doing something, for demo purpose.

Note that if we fetch data from the Internet, we would only set up the AJAX call to do that, and register the callback function, but we won’t use any setInterval() or setTimeout().  The setInterval() here is merely to simulated doing something, such as doing some complex computations or task that may take a few seconds or more.

Now, let’s also add the observer that goes ahead and register with the promise that, when something goes wrong or you cannot keep the promise, let me know:

http://jsfiddle.net/KennethKinLum/tvsqoo27/4/

promise.catch (function () {
    $("body").append("Person A: wow I just know that the promise was not kept, at " + (new Date()).toLocaleTimeString() + "</div>"); 
});

So now let’s pretend that some calculations are done every second, by just generating some random number from 0 to 9999.  When the number is greater than 9000, we treat it as: we finally finished the calculations and now can provide you with the data we promised you:

http://jsfiddle.net/KennethKinLum/tvsqoo27/5/

var i = Math.round(Math.random() * 10000);

if (i > 9000) {
    honor_with(i);
    clearInterval(timerID);
}

The clearInterval() is to stop this function from being called again.

Note that when the script runs (and you can run it several times to see), the result window will show that the “worker” may be working, and no promised data is provided yet. But after several lines of such message, if the random number is greater than 9000, then the observer will be notified about the promised data. This is done by the worker invoking honor_with(i), or in a more traditional terminology: resolve(i).

Now let’s pretend that something could go wrong, if fetching the data from the Internet or some calculation resulted in an error, then how to we say we can’t keep the promise:

http://jsfiddle.net/KennethKinLum/tvsqoo27/6/

if (i > 9000) {
    honor_with(i);
    clearInterval(timerID);
} else if (i < 1000) {
    not_keep();
    clearInterval(timerID);
}

So we simulated it by checking if the random number is less than 1000. If so, we pretend that it is some kind of error, and invoke not_keep(). In a more traditional terminology, it is: reject().

So that’s it. The overview is, a promise is an object that will promise to have some data or finish some lengthy task, and any number of observers can say: yes, I am interesting in knowing this data at a later time, and interesting in knowing when you cannot keep the promise — please notify me when it happens. You will also see in the result window, that Person A is the user of the promise object, while person B is worker, to find the data or to do some lengthy task.

In jQuery, the promise object and the resolve, reject functions are lumped together, as a deferred object. It is described as: the deferred object is a superset of the promise object. So the deferred object can notify the observers by a resolve() or reject(). At the same time, the observers can register with the deferred object that they are interested to be notified.

However, it is much more proper to pass around the promise object (not the deferred object) so that the observers can register. If you pass around the deferred object, who know whether those observers might do a resolve or reject incorrectly? Supposedly, only the worker should resolve or reject, but the user of the promise only register themselves to observe it, not to resolve or reject it.

As Terry Jones and Nicholas Tollervey say in the book on jQuery Deferreds, it is "create a deferred, but return a promise."

I like to think of it this way: the Deferred class is a blueprint to instantiate a deferred object.  The deferred object encapsulates the capabilities of: (1) giving out the promise object (which is associated with the promised value or task), so that it can be observed by others, and (2) setting the state of the promise to be completed or incomplete, by using the resolve or reject methods, which in turn will notify the observers.

To visualize it, it can be thought of as a person, let's call him Mr. D for Deferred.  You come to Mr. D for a result, and he will give you a beeper to notify you when it is ready (or when the result can't be given), and it is like how you go to a restaurant and they give you a beeper to notify you when a table is ready.  Now Mr. D also accepts two messages.  One is a resolve message, to tell him, yes, the result is ready and it is ______.  The other message Mr. D accepts is a reject, meaning that the result can't be provided.  When Mr. D takes either of these messages, then he will notify all people who took a beeper.  This beeper is like the promise.  Mr. D is the deferred.

In jQuery, if we already have a deferred object:

var deferred = $.Deferred();

Then to get the promise object, we can invoke the promise() method on the deferred object:

var promise = deferred.promise();

Also note that since jQuery 1.5, jQuery.ajax(), or $.ajax() returns a jqXHR object, which implements the promise interface. So we can actually treat it as a promise, in such a way:

$.ajax({ ... }).done(fn1).fail(fn2).always(fn3);

Note that there are 3 states of a promise object. Before any result is known or before the task is completed, the state is pending. When the task is completed as a success, the state of the promise object shall be set as resolved. And when some error has occurred, then the state of the promise object shall be set as rejected.  So a promise is always in one of these 3 states: pending, resolved, or rejected.

If we use jQuery’s Deferred and Promise to write the code, it will be something like:

http://jsfiddle.net/KennethKinLum/sd67Lm8f/6/

var deferred = $.Deferred(),
    promise = deferred.promise();

var timerID = setInterval(function () {

    var i = Math.round(Math.random() * 10000);

    if (i > 9000) {
        deferred.resolve(i);
        clearInterval(timerID);
    } else if (i < 1000) {
        deferred.reject();
        clearInterval(timerID);
    }

    $("main").append("Person B: I am thinking or not doing anything, at " + (new Date()).toLocaleTimeString() + "\n");

}, 1000);

promise.done(function (foo) {
    $("main").append("Person A: wow I just know that the promise was kept, with the data being " + foo + ", at " + (new Date()).toLocaleTimeString() + "\n");
});

promise.fail(function () {
    $("main").append("Person A: wow I just know that the promise was not kept, at " + (new Date()).toLocaleTimeString() + "\n");
});

Using jQuery, we can also observe how much the promise is done: by progress.

Consider the following situation: the promise is to talk 30 steps or more with not a single time that 10 steps are walked. Each second, he will walk 1 to 10 steps. But once he found he walked exactly 10 steps at one time, he will consider it too much and declare the promise is not kept. When he has walked 30 steps or more and every time it is not exactly 10 steps, then he will consider the promise is kept.

We can use jQuery deferred’s notify() method, which is to notify any interested observer of any progress. The observer will register itself using the progress() method, on the promise:

http://jsfiddle.net/KennethKinLum/sd67Lm8f/7/

var deferred = $.Deferred(),
    promise = deferred.promise();

var totalSteps = 0;

var timerID = setInterval(function () {

    var singleSteps = 1 + Math.floor(Math.random() * 10);

    totalSteps += singleSteps;

    deferred.notify({
        singleSteps: singleSteps,
        totalSteps: totalSteps
    });

    if (singleSteps === 10) {
        deferred.reject();
        clearInterval(timerID);
    } else if (totalSteps >= 30) {
        deferred.resolve(totalSteps);
        clearInterval(timerID);
    }

}, 1000);

promise.done(function (foo) {
    $("main").append("Person A: wow I just know that the promise was kept, with " + foo + " steps walked, at " + (new Date()).toLocaleTimeString() + "\n");
});

promise.fail(function () {
    $("main").append("Person A: wow I just know that the promise was not kept, at " + (new Date()).toLocaleTimeString() + "\n");
});

promise.progress(function (info) {
    $("main").append("Person A: wow Person B told me he just walked " + info.singleSteps + " steps, for a total of " + info.totalSteps + " steps, at " + (new Date()).toLocaleTimeString() + "\n");
});

To show a progress bar by using the HTML5 progress element, we can use

promise.progress(function(info) {
  $("#walking-progress").val(info.totalSteps / totalStepsToFinish);
});

and a demo is in here:

http://jsfiddle.net/KennethKinLum/sd67Lm8f/13/

JavaScript's Pseudo Classical Inheritance diagram

The following is a chart of JavaScript Pseudo Classical Inheritance.  The constructor Foo is just a class name for an imaginary class.  The foo object is an instance of Foo.

Note that the prototype in Foo.prototype is not to form a prototype chain.  Foo.prototype points to some where in a prototype chain, but this prototype property of Foo is not to form the prototype chain.  What constitute a prototype chain are the __proto__ pointing up the chain, and the objects pointed to by __proto__, such as going from foo.__proto__, going up to foo.__proto__.__proto__, and so forth, until null is reached.

JavaScript's Pseudo Classical Inheritance works like this way: I am a constructor, and I am just a function, and I hold a prototype reference, and whenever foo = new Foo() is called, I will let foo.__proto__ point to my prototype object.  So Foo.prototype and obj.__proto__ are two different concepts.  Foo.prototype indicates that, when an object of Foo is created, this is the point where the prototype chain of the new object should point to -- that is, foo.__proto__ should point to where Foo.prototype is pointing at.

In the ECMA-262 Edition 5.1 spec, the term [[Prototype]] is used.  And that's the same as __proto__.  It is often mentioned as the "[[Prototype]] internal property".  And don't confuse this with a function's prototype property.  One of the key points regarding [[Prototype]] is: "All objects have an internal property called [[Prototype]]. The value of this property is either null or a reference to an object and is used for implementing inheritance."

And now we can see from the diagram why when we inherit Dog from Animal, we would do:

    function Dog() {}    // the usual constructor function
    Dog.prototype = new Animal();
    Dog.prototype.constructor = Dog;

It is to say: first of all, define a function Dog.  This function is an object, as every function in JavaScript is an object.  Now, add a property prototype to the object Dog.  And then, new Animal() will create a new object (and it will become part of the prototype chain), and since this new object is created using the Animal constructor, this new object's __proto__ will point to where Animal.prototype is pointing to.  Now, make Dog.prototype point to this new object.  And that's how the object pointed to by Dog.prototype is created as shown in the diagram.

(Note: with the introduction of Object.create(), it can also be done this way:

    Dog.prototype = Object.create(Animal.prototype);

which is to say, Dog.prototype.__proto__ should point to Animal.prototype.)

Next, since that new object was created by the Animal constructor, the new object's constructor property will point to Animal (an object created by constructor Foo will have a constructor property pointing to Foo).  This constructor property is not Dog.prototype's own property -- it is the own property of Dog.prototype.__proto__, so it is an inherited property.  Note that in this case, we actually want the Dog.prototype object's constructor property to point to Dog, and that why we have the second line of code above: Dog.prototype.constructor = Dog;

Note that we can use an empty function F() to set up the above relationship as well:

    function Dog() {}    // the usual constructor function
    function F() {}
    F.prototype = Animal.prototype;
    Dog.prototype = new F();
    Dog.prototype.constructor = Dog;

Because Animal() may take a longer time or more complex logic to run, and it can also create properties in that new object that we don't need.  A way to set up the Dog.__proto__ to point at Animal.prototype is what we need, and F() can already accomplish that.

If there are 3 Dog instances, they would point to the middle of that long prototype chain.  It is still a complete prototype chain, but a shorter one:

Now we can understand why when we add a method to the Animal class, we would use

    Animal.prototype.move = function() { ... };

That's because when we say

    woofie.move();

If woofie the object doesn't have the move method, it will go up the prototype chain, just like any prototypal inheritance scenario, first to the object pointed to by woofie.__proto__, which is the same as the object that Dog.prototype refers to.  If the method move is not a property of that object (meaning that the Dog class doesn't have a method move), go up one level in the prototype chain, which is woofie.__proto__.__proto__, or the same as Animal.prototype.  Remember we already did

    Animal.prototype.move = function() { ... };

earlier, and so now move is found, and the method can be invoked.

Note again that this is how prototypal inheritance works, and see how "classical inheritance" is simulated: by the help of prototypal inheritance.

Using the diagram, we can also see the working of instanceof.  For foo instanceof Animal, it is true, because we take foo and look at the whole prototype chain, and the Animal.prototype object is part of that chain.  Therefore, it returns true.  woofie instanceof Animal is true for the similar reason: take woofie's whole prototype chain, and the Animal.prototype object is part of that chain.  woofie instanceof Bichon is false because the Bichon.prototype is not part of that chain.  Note that woofie.__proto__ instanceof Animal is true, the same as Dog.prototype instanceof Animal, because instanceof checks for whether the right operand's prototype object is part of the left operand's prototype chain. (Note that Dog.prototype instanceof Dog used to be true, but it has changed in later implementation of JavaScript: so it will go up to see if Dog.prototype is part of the chain, but it won't include the object itself (the left operand) to check against Dog.prototype).

Note that in reality, each constructor function has a __proto__ property as well, and if the Function constructor is also shown here,  a more complete picture is:

Even though foo.constructor === Foo, the constructor property is not foo's own property.  It is actually obtained by going up the prototype chain, to where foo.__proto__ is pointing at.  The same is for Function.constructor.  The diagram can be complicated, and sometimes confusing when we see Constructor.prototype, foo.__proto__, Foo.prototype.constructor.  Note that Firefox, Chrome, Safari, and node.js support __proto__, but IE doesn't support it, and it can be obtained by Object.getPrototypeOf(foo).  (IE 9 or above is needed.  Before IE 9, it can be defined as in John Resig's post, and it requires that the constructor property is set properly.)  To verify the diagram, note that even though foo.constructor will show a value, the property constructor is not foo's own property, but is obtained by following up the prototype chain, as foo.hasOwnProperty("constructor") can tell.