On Tue, 11 Sep 2012, Vincent Hanquez wrote:
On 09/11/2012 07:27 PM, Ben Millwood wrote:
As an aside, the major reason I support HTTP over something like http-conduit is the latter's titanic dependency list. I think especially as a dependency of cabal-install that's something of a dealbreaker:
$ cabal install http-conduit | grep 'new package' | wc -l [...] 47
I'm not sure what do you want to demonstrate here, number of packages couldn't be a more irrelevant metric. Would you prefer a package that includes everything in one giant codebase ?
I also hesitate to depend on packages with very many dependencies - although I write such packages myself. Chances are high that one of the imported packages fails to compile on a certain system or compiler version.
For example, the whole haskell TLS stack is responsible for at least 10~15 packages in http-conduit's list.
I haven't checked whether it is possible, but maybe there are ways to let the user plug in the TLS functionality if he needs it. Then conduit-http would not need to depend on it.