Haskellers agree, that's why we have Template Haskell. We use it for all sorts of things, like automatically implementing typeclasses (interface'ish) at compile-time.
> parallelism, sure Haskell can give that for free
Not really.
>The cost is you have to be pure about everything
Nonsense.
Boom, mutable variables:
http://bitemyapp.com/posts/2014-03-25-when-nested-io-actions...
>sometimes you want explicit control over your threads.
You can have that in Haskell. You can use green threads or OS threads and optionally pin OS threads to a particular CPU to avoid context-switching.
So you can know what you're talking about next time, my recommended guide for Haskell:
https://gist.github.com/bitemyapp/8739525
The concurrency primitives in Haskell are broad and deep, check this book out: http://chimera.labs.oreilly.com/books/1230000000929
--- an ex-Lisper
I like your guide, but is this really necessary? This isn't the first time you've been aggressively hostile to people expressing a preference for Lisp over Haskell, either.
Also you can't express a preference (up or down) for something you've never used.
I'll elide the snark next time, but I'm not going to stop correcting false statements or sharing learning resources.
> I have no doubts the Haskell community is great.
You're not making a strong case for it, are you? ;-)
Would be nice if the culture could shift a notch or two towards, "know nothing -> say nothing" though.
As far as parallelism, sure Haskell can give that for free. The cost is you have to be pure about everything, which just seems obnoxious to me...especially when you don't necessarily care about parallelism or performance.
With lisp, I can use macros to make parallelism just as natural as programming regular lisp. Yes, I have to be explicit about when I'm being parallel and when I'm not. But that doesn't seem like such a big deal to me, and sometimes you want explicit control over your threads.
As far as community, I have no doubts the Haskell community is great. But so is the lisp community. There are a lot of bright people who jump at any chance to help out others, and in the past 5 years the CL implementations and community-built libraries have been making leaps and bounds.
This isn't to say Haskell isn't a great choice for many, many applications and requirements. But it's not a replacement for lisp, just as lisp isn't a replacement for Haskell. They are two different beasts that are great at different things.