F# and Haskell, Estranged Cousins

#1

Post by Minerick » Thu, Jan 29, 2009, 9:10 PM UTC

F# and Haskell, Estranged Cousins
atalasoft.com

Re: F# and Haskell, Estranged Cousins

#2

Post by prospero » Thu, Jan 29, 2009, 10:50 PM UTC

Unfortunately, OCaml only has lightweight threads, and F# isn't very performant in a non-Windows environment. I'm not sure there's really a clear winner here.

Re: F# and Haskell, Estranged Cousins

#3

Post by felixmar » Thu, Jan 29, 2009, 11:19 PM UTC

prospero wrote: post #2

Unfortunately, OCaml only has lightweight threads, and F# isn't very performant in a non-Windows environment. I'm not sure there's really a clear winner here.

Take a look at this picture: http://www.csharp-architect.com/images/MonobenchmarksIncLinu...

Mono performs pretty good in comparison to Microsoft's runtime. The garbage collector still needs some work, but it would not surprise me if Mono becomes very competitive in the near future.

Re: F# and Haskell, Estranged Cousins

#4

Post by critic » Fri, Jan 30, 2009, 3:14 AM UTC

> The most obvious difference between Haskell and F# is somewhat easy to infer from this graph: object oriented constructs. That is to say, OCaml pioneered the use of object oriented data structures in functional programming and F# is it’s direct descendant.

Uninsightful. OO in F# is unrelated to OO in OCaml.

Re: F# and Haskell, Estranged Cousins

#5

Post by malkia » Fri, Jan 30, 2009, 6:48 AM UTC

Jon Harrop To The Rescue! Hey Jon! Hey.... Ah... disappeared...

Re: F# and Haskell, Estranged Cousins

#6

Post by rincewind » Fri, Jan 30, 2009, 10:26 AM UTC

This reminds me of the distinction between "systems" and "theory" in http://news.ycombinator.com/item?id=436058

Re: F# and Haskell, Estranged Cousins

#7

Post by Minerick » Fri, Jan 30, 2009, 6:13 PM UTC

felixmar wrote: post #3

prospero wrote: post #2

Unfortunately, OCaml only has lightweight threads, and F# isn't very performant in a non-Windows environment. I'm not sure there's really a clear winner here.

Take a look at this picture: http://www.csharp-architect.com/images/MonobenchmarksIncLinu... Mono performs pretty good in comparison to Microsoft's runtime. The garbage collector still needs some work, but it would not surprise me if Mono becomes very competitive in the near future.

That is extremely interesting. I would also like to see a graph of the percentage of APIs implemented and some kind of metric for the amount of testing for each API.

Thanks for the link.