Mega-module?
wc *._js */*._js
613 2854 18723 api._js
45 177 1350 devices/array._js
54 236 1716 devices/buffer._js
25 63 575 devices/console._js
42 156 1263 devices/file._js
43 127 920 devices/generic._js
29 129 1173 devices/http._js
36 176 1605 devices/net._js
37 130 1178 devices/node._js
32 86 750 devices/std._js
55 241 1706 devices/string._js
52 220 1671 transforms/csv._js
184 787 5472 transforms/json._js
51 216 1530 transforms/lines._js
106 433 3560 transforms/multipart._js
1404 6031 43192 total
To which you need to add streamline-streams
932 3678 30258 streams._js
And this is code + API documentation because the API doc is extracted from
the code.
I could have packaged it as 15 different packages (one for the general API
+ 1 per device/transform). I don't think that's any easier.
If you are looking for a simple API to implement a stream. What would be
simpler than
exports.myStream = ez.devices.generic(function read(cb) {
// your stream implementation here...
});
I had seen Tim's simple-stream but I had missed min-stream. It looks very
similar in scope. Differences in the naming. EZ is more closely aligned on
ES5 Array (was my starting point) and treats all the callbacks (what you
pass to map, filter, transform, ...) as async functions. But the sprit is
definitely the same.
Dominic's pull-streams looks closer to the low level streamline-streams API
which has been around for a long time.
Bruno
On Tuesday, December 17, 2013 10:41:29 AM UTC+1, Floby wrote:
>
> that readme is a bit too long to be EZ =)
>
> Personnally, I like tiny modules, so the ez mega module frightens me a
> little. It makes me think of Boost in the C++ world.
> However I like being able to write streams more easily (even though I got
> used to streams2 in the end).
>
> I can't make out the fundamental design differences between ez-stream and
> Tim Caswell's min-stream <https://github.com/creationix/min-stream> and
> simple-stream <https://gist.github.com/creationix/5902825>, and Dominic
> Tarr's pull-stream <https://github.com/dominictarr/pull-stream>
>
> All in all, I'd like to see a simpler stream API for implentors (simple as
> in simple made easy <http://www.infoq.com/presentations/Simple-Made-Easy>)
> but I really don't know which one to choose right now. So I stick to the
> node core's one.
>
> On Tuesday, 17 December 2013 03:05:17 UTC+1, Bruno Jouhier wrote:
>>
>> Just published first brew of ez-streams to NPM: Easy streaming API for
>> node.js.
>>
>> http://bjouhier.wordpress.com/2013/12/17/easy-nodejs-streams/
>> https://github.com/Sage/ez-streams
>>
>> Bruno
>>
>
--
--
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
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
