tag:blogger.com,1999:blog-2655510740205693038.post8897707373047904947..comments2008-10-30T08:29:57.161-07:00Bilzmoudehttp://www.blogger.com/profile/00821599794835500923noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2655510740205693038.post-15329827249763019022008-10-30T08:29:00.000-07:002008-10-30T08:29:00.000-07:00I don't know that I agree completely. Yes, the parallel problem is well understood, but why don't we see a C# compiler (for instance) that runs your code in parallel?<BR/><BR/>The compiler doing the work is exactly my point here. With a functional programming language, your compiler can split the work for you... It is a much easier problem to solve when you are not telling your hardware how to solve the problem, and let the compiler do it for you. <BR/><BR/>With functional programming, the problem gets a lot easier.Brianhttp://www.blogger.com/profile/09870893143113928241noreply@blogger.comtag:blogger.com,1999:blog-2655510740205693038.post-1689334723639918142008-10-30T06:11:00.000-07:002008-10-30T06:11:00.000-07:00Hmm - sounds like you been drinking too much Koolaid:) I've looked at functional programming off and on - and always wondered "Why would I want to do it that way?" The are many other well understood techniques to solve the parallel problem, hardware (chip design), software (OS and compilers), etc.MadHungarianhttp://www.blogger.com/profile/08282402827359862010noreply@blogger.comtag:blogger.com,1999:blog-2655510740205693038.post-51360305023072804832008-10-30T05:22:00.000-07:002008-10-30T05:22:00.000-07:00Sounds like a great mindset. Dustin Campbell has been writing about F# for quite some time now... You can check it out at: http://diditwith.net/Bretthttp://www.blogger.com/profile/09897293833393658648noreply@blogger.com