Raynos, I have a feeling that you are comparing apples and oranges. Streams are awesome, Promises are awesome but it's not the same, and not every use case can be addressed on equal level by both of them.
>From my experience there can be promises that are also a streams, but among them are also promises that fulfill before stream ends. There can also be promises that are not streams, of course you may represent them as stream but if they bring no value and just emit 'end', it doesn't fit well stream concept, does it? Same way you can just use callbacks instead of promises, but the point is that promises gives you better abstraction, so it's easier to construct complicated flow with it and maintain it. See this: https://github.com/medikoo/deferred#promises-approach How would you write it with streams instead? Would it be more friendly than callbacks version: https://github.com/medikoo/deferred#plain-nodejs ? On Wednesday, October 3, 2012 6:40:02 AM UTC+2, Raynos wrote: > > https://github.com/Raynos/promise-stream > > If you want to turn a stream into a promise you can. > > This mainly illustrates how streams and promises are similar for those > that like promises. > > It also shows a comparison between how you flow async code through > promises and streams > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
