<br><br><div><span class="gmail_quote">On 7/10/07, <b class="gmail_sendername">Sebastian Sylvan</b> <<a href="mailto:sebastian.sylvan@gmail.com">sebastian.sylvan@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
While I personally think that the productivity argument should be<br>enough to "make the switch", the killer-app (the app that will kill C,<br>that is :-)) is concurrency. C is just not a tractable tool to program
<br>highly concurrent programs, unless the problem happens to be highly<br>amenable to concurrency (web servers etc.). We need *something* else.<br>It may not be Haskell, but it will be something (and it will probably<br>
be closer to Haskell than C!).<br></blockquote></div><br>Yeah I agree with this. C# totally rocks, but threading is an unsolved problem.<br><br>If you can get to the stage where you can get a non-optimized, readable/maintainable Haskell program to run at more than say 30% of the speed of a non-optimized, readable/maintainable C# program, but automatically runs across 16 or 256 cores, then you're on to a winner.
<br><br>