Haskell is more about inverting the responsibility. Just code up whatever in Haskell and it might be slow, but there are a whole bunch of errors that code just

Haskell is more about inverting the responsibility. Just code up whatever in Haskell and it might be slow, but there are a whole bunch of errors that code just can't have. When you need the big unsafePerformIO hammer, it's there for you. Anybody can write fantastic threaded code in any language if they think real hard about it. Haskell just makes you say, "Yes indeed i did think really hard about it. I'm not just checking this in on friday afternoon so the boss doesn't bug me." I'm not real familiar with erlang, but IIRC it has very similar appeal to a higher power semantics. This may or may not be useful, depending on the kind of work you do. I ,for one, am often undisciplined but occasionally very clever. Given that, the Haskell model is very enjoyable ; I've never used it to make money though. So there's that.