- From: Anders Riutta <notifications@github.com>
- Date: Sat, 30 Jul 2016 09:46:38 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Message-ID: <whatwg/streams/issues/461/236375655@github.com>
pull-stream looks cool! Regarding transformations, one concern for web streams is that today's parser and converter ecosystem is geared for other streams/iterators, predominantly Node streams. If I'm writing a new parser, I'd love for it to be usable by everyone, regardless of their preference for stream/iterator implementation. But limited time on my part means I'm not going to write a version for every stream/iterator implementation. That means I'll probably write my new parser for either 1) Node streams, because that's where most users are or 2) transducers, because then it's usable with [native or Underscore reduce implementations](https://github.com/cognitect-labs/transducers-js#integration), [immutable-js](https://github.com/jlongster/transducers.js?files=1#immutable-js) [Node streams](http://highlandjs.org/#transduce), [RxJS](https://github.com/Reactive-Extensions/RxJS/blob/master/doc/gettingstarted/transducers.md), etc. It would be great if the transformation option for web streams made it easy for me when I'm writing that new parser. Could the transformation option simply be a `transduce` operator? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/461#issuecomment-236375655
Received on Saturday, 30 July 2016 16:47:08 UTC