On 7/17/07, <b class="gmail_sendername">Thomas Conway</b> &lt;<a href="mailto:drtomc@gmail.com">drtomc@gmail.com</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And this is where I think Haskell has it all over C++, Java, and the<br>rest. Haskell is easy to learn at a simple level, and hard to learn at<br>the expert level, but once learned is very powerful and has excellent<br>payoffs in terms of productivity. With C++ or Java, the expertise is
<br>somewhat easier to acquire, but you never get the payoff. And before<br>you all flame, yes, I do know C++ at an expert level, and that is<br>exactly why, after 7 years of writing server software in C++, I now<br>want to do it in Haskell.
<br></blockquote></div><br>You know, it just occurred to me: I get the feeling that many Haskell programmers are ex-C++ programmers, which makes a certain amount of sense because C++ is insanely hard to debug and maintain, because of stack/heap corruption, and lack of a GC.
<br><br>Am I the only person who finds it interesting/worrying that there are few to no people in the group who are ex-C# programmers.&nbsp; I mean, you could argue that C# programmers are simply too stupid to do Haskell, but ... you know, there is another explanation ;-)
<br><br>