README: perhaps illustrate the problem and why q is the solution about q HOT 5 CLOSED

I humbly submit my presentation as either a link to include, or as a source from which examples can be plagiarized at will.

from q.

@jrburke I like the idea of a problem statement, but I hesitate to characterize the benefits of using promises to just addressing the pyramid of doom, particularly because other libraries like @caolan’s async do that job pretty well. It’s a worthy problem to solve, but error propagation, reducing "chat delays" in distributed programs, POLA, and OCap philosophy are all part of the value. What you see is just the beginning: promise-aware debuggers and visualizers, progress monitors, cancellation propagation, and such other things fit in the architecture of a promise library.

@DomenicDenicola I think lifting examples is the better strategy. A lot of the preamble is specific to folks coming from ".Net". I want to keep the sale’s pitch in the README, and I think the tutorial is it. We could rotate the reference and examples out and into the Wiki.

from q.

@kriskowal Agreed. I think slides 42--68 are the most relevant.

from q.

@kriskowal sure. for me as a newbie, the pyramid of doom was enough to get me into q, but I'm really fine with whatever you think might work. I am just suggesting giving a bit more context before talking about promises. In any case though, thanks for the README update!

from q.

@jrburke I’ll give it a shot. Thanks for the idea.

from q.