<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Le 20/06/2013 18:08, Mark Miller a
      écrit :<br>
    </div>
    <blockquote
cite="mid:CAK5yZYhTnVsOmZJctFxyk=_ZABn_xaWn_qG6F+WFH0VBXuRPCQ@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Thu, Jun 20, 2013 at 7:50 AM,
            David Bruant <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:bruant.d@gmail.com" target="_blank">bruant.d@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <div>Le 20/06/2013 14:55, Forbes Lindesay a écrit :<br>
                </div>
                <div class="im">
                  <blockquote type="cite">
                    <div>
                      <p class="">I’ve been answering quite a few
                        questions about promises on stack overflow
                        lately.</p>
                    </div>
                  </blockquote>
                </div>
                Do you have a link to a list to these questions (and/or
                your answers) off-top your browser history by any
                chance?
                <div class="im"><br>
                  <br>
                  <blockquote type="cite">
                    <div>
                      <p class="">One of the key things people seem to
                        struggle to get their head around is the idea of
                        `.then` as being something that transforms the
                        promise and returns a new promise.  They either
                        expect it to mutate the existing promise or they
                        expect it to behave like `.done()` does.</p>
                    </div>
                  </blockquote>
                </div>
                I wasn't there when that started, but it feels like
                "then" organically grew out of the experience of using
                promises a lot which naturally leads to promise
                pipelining.<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div style="">I'm worried that you may be suffering from and
              spreading a terminology confusion. "Promise pipelining" is
              an important latency reduction optimization when using
              promises over a network. See Chapter 16 of <<a
                moz-do-not-send="true"
                href="http://erights.org/talks/thesis/markm-thesis.pdf">http://erights.org/talks/thesis/markm-thesis.pdf</a>>.
              Using .then, either with or without the return result, *<b><i>prevents</i></b>*
              promise pipelining, which is another reason to emphasize
              asynchronous message sending and deemphasize .then.</div>
            <div style=""><br>
            </div>
            <div style="">From context, I suspect you're talking about
              "promise chaining".<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Yes, I meant "chaining". Sorry for the confusion.<br>
    <br>
    David<br>
  </body>
</html>