David Leimbach wrote: > On Wed, Aug 4, 2010 at 3:16 AM, Alberto G. Corona > <agocor...@gmail.com>wrote: > >> Just to clarify, I mean: Haskell may be seriously addictive. Sounds >> like >> a joke, but it is not. I do not recommend it for coding something quick >> and >> dirty. >> > > I use it for quick and dirty stuff all the time, mainly because what I > want > is often something that can be broken down into stages of processing, and > pure functions are really nice for that. > > If I know the input is coming from a reliable enough stream (like a unix > pipe to stdin) I can use functions like "interact" to create filters, or > parse some input, and produce some output. > > It's pretty nice. >
I may be mistaken (in which case, I'm sorry for putting words in his mouth) but I understood what he was saying not as that Haskell is not suited for quick and dirty projects, but rather that Haskell for small projects could be a dangerous "gateway drug" that could seriously impact one's ability to continue to enjoy working in other languages. -- James _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe