jQuery: What is the difference between deferred.always() and deferred.then()?

Question

Seems to me that both does the same thing.

Docs:

• deferred.always()

• deferred.then()

Answer 1

It would seem that deferred.then() allows you to pass two separate callbacks for success and failure, whereas deferred.always() takes n number of callbacks which will all be called regardless of the outcome of the initial event.

I would say use deferred.always() in the cases where success/failure of the initial event are not important

Answer 2

With .then() you can provide an individual callback for when the $.Deferred is resolved (done), and another for when the $.Deferred is rejected (fail).

.always(), on the other hand, allows you to provide a callback that always gets executed, whether the $.Deferred has been resolved or rejected. In other words, within this callback, it doesn't matter if the AJAX call has failed or has been been successfully executed.

I tend to put code in .always() when I want that code to run everytime, and independently of whether the $.Deferred was resolved successfully or not. For example, to clear an AJAX loading indicator or to hide a progress bar. Using .then() you'd have something like this:

$.get("/some/url").then(function () { // done callback   $(".progress-bar").hide(); }, function () { // fail callback   $(".progress-bar").hide(); }); 

Whilst if you used .always(), you'd just need a single callback, because you always want to hide the progress bar, no matter if the $.Deferred was resolved or rejected:

$.get("/some/url").always(function () {   $(".progress-bar").hide(); });