First crack at a Streams proposal

Tab Atkins Jr. jackalmage at gmail.com
Mon Apr 15 19:12:56 PDT 2013


On Mon, Apr 15, 2013 at 5:37 PM, Andrea Giammarchi
<andrea.giammarchi at gmail.com> wrote:
> how about .pull() then, to read, and .push() to write :D

Node experience notwithstanding, long experience with Promises/etc
showed that mixing the promise and the resolver in a single object is
a bad idea.  I expect the same to be true of streams, which is why I
designed the constructor analogously to Future, as it produces a
strict and hard-to-accidentally-violate separation.

~TJ


More information about the es-discuss mailing list