* Felipe Almeida Lessa <felipe.le...@gmail.com> [28.06.2012 01:00]: > (Disclaimer: I work closely with Michael Snoyman, conduit's author.)
I know that but the community has always been grown enough that this doesn't matter ;-) > > On Tue, Jun 26, 2012 at 2:33 PM, Christian Hoener zu Siederdissen > <choe...@tbi.univie.ac.at> wrote: > > it seems that the conduit package is used more often now and dependent > > packages maintained (just had a problem with iteratee-compress) better > > than with iteratee. > > > > Does this seem correct? > > > > Can I expect conduit to be the new standard in iteratee-based stuff? (At > > least for Biohaskell?) It seems that Felipe is using conduit, while > > Nicholas is maintaining enumerator+iteratee bindings? > > IMHO conduit is the best you can get right now. It's much simpler to > use than enumerator, which was already simpler than iteratee. Well, as will all packages one has to understand how to write certain stuff. I have to say, in defense of iteratee, that once you know it, it is very nice to use. Especially in a monadic environment. I still need to learn conduit. > It's used in the real world by many people, unlike pipes which isn't > being used anywhere I know of. It suffers a lot of bashing even from > people who don't like it =), and Michael is a very responsive and nice > maintainer. I'll not start any comments. I know neither conduit nor pipes, only the older ones (iterIO, enumerator, iteratee). When I started iteratee won due to "zip". > > WRT libraries, many of the conduit libraries are maintained by the > Yesod team, including lower level ones like conduit itself and > resourcet, and higher-level ones like http-conduit, > attoparsec-conduit, xml-conduit, etc. These are mostly high quality > libraries. Some have older enumerator counterparts that are either > deprecated or defunct. Other conduit libraries are the mix and match > Hackage is, including my own biostockholm =P. Actually, iteratee-compress doesn't compile in certain settings due to not being maintained (?) and that set of my warning system to consider switching. Well-maintained core libraries (attoparsec, zlib) are a need, so conduit looks good here. I'd rather nobody ever invented xml, but since it is not going away and some bio people store xml data instead of using or defining a good format, I'm happy that a library for that is available, too. > > As selfish as it sounds, I don't plan on working outside conduit > unless I need to =). Why would that be selfish? > > > Finally, anybody (Felipe?) use conduit/list.zipSinks yet? > > Never needed to use it myself, did you find anything wrong with it? No, it's just that I have an important use case for it. Two or more sinks creating data structures from multigigabyte files, not necessary in lock-step. And it could just happen that I can /not/ go twice over the data as I have a the program in a linux-pipe. Gruss, Christian
pgph3EhLFL0GU.pgp
Description: PGP signature
_______________________________________________ Biohaskell mailing list Biohaskell@biohaskell.org http://malde.org/cgi-bin/mailman/listinfo/biohaskell
