Difference in fail semantics between jQuery promises and WinJS promises

gistfile1.js

// jQuery - failures persist along the chain
$.Deferred(function(d) { d.reject() })
    .then(function() { console.log("Success handler 1") }, function() { console.log("Fail handler 1") })
    .then(function() { console.log("Success handler 2") }, function() { console.log("Fail handler 2") });

// Output:
// Fail handler 1
// Fail handler 2

// ------------------------------------------------------------------------------------------------------
// WinJS - failures are swallowed by the first handler and then ignored

new WinJS.Promise(function(complete, err) { err() })
    .then(function() { console.log("Success handler 1") }, function() { console.log("Fail handler 1") })
    .then(function() { console.log("Success handler 2") }, function() { console.log("Fail handler 2") })

// Output:
// Fail handler 1
// Success handler 2

The difference is actually the meaning of then. jQuery's then is weird. Use pipe instead; it's the same as WinJS's then.