There seems to be a large number of new users (a few of which were created within 5 minutes of this submission) who've only commented on this, and very vacuously.
<p><pre><code> p1.and( p2 ).then( function( p1_result, p2_result ){...});
</code></pre>
I believe this is equivalent to:<p><pre><code> Q.all( p1, p2 ).spread( function( p1_result, p2_result ){ ... } );
</code></pre>
There are other good reasons, at this point, to switch from Q to another promise lib, speed for example, as was virulently signaled recently: <a href="http://jsperf.com/wqfwewefewrw/4" rel="nofollow">http://jsperf.com/wqfwewefewrw/4</a>
I like the idea, but am I the only one who feels that having a method 'and' feels a little too... cute?<p>I mean, it's not at all obvious that 'and' is related to parallel execution, and it could very easily clash with another library that uses the same name.