Re:Haskell in Production: The good, the bad, and the ugly
by davidw on Wednesday October 31, 2012 @05:48AM
(#4721993)
> But the biggest reason of using haskell for me, was the way it handles concurrency and the high abstraction level.
Anyone care to point to something online that spells these out in (simple) details for someone who knows next to nothing about Haskell?
Re:Haskell in Production: The good, the bad, and the ugly
by danieldk on Wednesday October 31, 2012 @06:02AM
(#4722026)
Simon Peyton Jones had a talk with a very nice overview of concurrency in Haskell. He is a very good presenter as well :).
Re:Haskell in Production: The good, the bad, and the ugly
by eklerks on Wednesday October 31, 2012 @06:15AM
(#4722066)
There are a lot of concurrency related libraries implementing all kind of abstractions. Distributed computation is upcoming. There is an overview here: http://www.haskell.org/haskellwiki/Applications_and_librarie...
Re:Haskell in Production: The good, the bad, and the ugly
by padrian2ss on Wednesday October 31, 2012 @10:54AM
(#4723058)
one big kick, since haskell is pure functional you don't have state (okay, in terms that imperative programmer use that term) and all data are immutable.
What I saw, was that the amount of tests could be reduced, when using haskell. The type of testing is also somewhat different. You don't have to test for type errors. QuickCheck let you test mathematical properties (in an empiric way).
The FFI compensates for the missing libraries, but is a bit difficult to use.
But the biggest reason of using haskell for me, was the way it handles concurrency and the high abstraction level. This enables you to write distributed applications in a more convenient way than usual. If you working in a web start up, you hit somewhere a point, where you need to think about this stuff.
Besides Yesod, Snap is also a interesting choice, because of it's simplicity.
I enjoy using this language. I would choose it anytime. It made me a better programmer.