thanks.It gave me a good understanding of what this is capable of. How is it in ...

DanielBMarkham · on Sept 12, 2009

I've anecdotally heard of F# kicking C#s butt when it comes to throughput, but you'll have to poke around on the web to find out more. Sorry I can't provide more details.

TY · on Sept 13, 2009

http://www.google.com/search?q=F%23%20better%20performance%2...

nearestneighbor · on Sept 12, 2009

> How is it in terms of performance ?

Same as C#, according to the author, but that probably presupposes that you'd be doing the same thing in both (equally imperative code).

DanielBMarkham · on Sept 12, 2009

Seems like I remember reading a blog where there were some gamer-programmers who had these huge log files to process. Using C# it was just too much -- it took too long. But by using F# (and block operations I think?) they reduced it to some crazy time like 5 minutes or something.

Theoretically they should be the same; they all run on the CLR. But I think F# lends itself to stuff like tail-recursion and data operations such that the code has a tendency to self-optimize as you write it, which is kinda neat.

nearestneighbor · on Sept 13, 2009

> Theoretically they should be the same; they all run on the CLR. But I think F# lends ...

I think you are misunderstanding this part. Tail call optimization can (sometimes) allow functional code be as fast as its imperative equivalent. It's not a magic bullet that makes it faster than the imperative code.