(Disclaimer: I work closely with Michael Snoyman, conduit's author.) 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. 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. 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. As selfish as it sounds, I don't plan on working outside conduit unless I need to =). > Finally, anybody (Felipe?) use conduit/list.zipSinks yet? Never needed to use it myself, did you find anything wrong with it? Cheers, -- Felipe. _______________________________________________ Biohaskell mailing list Biohaskell@biohaskell.org http://malde.org/cgi-bin/mailman/listinfo/biohaskell
