I actually think it's catch-22 with popularity as well as being a bit niché. * When choosing language/platform for enterprise projects (where .Net is most com

I actually think it's catch-22 with popularity as well as being a bit niché. * When choosing language/platform for enterprise projects (where .Net is most commonly used) the company will go with one where they can find/have talent and resources. There's not many F# developers out there so you're severely limiting yourself. * Since C# is more popular and has better tooling there has to be a substantial advantage of using F# instead. From what I can see that may only happen in certain financial and engineering solutions where minimizing the risk of errors, unit conversions, calculations etc is severe (Lose a couple of million dollars/Challenger-explosion -severe). Those projects are pretty far between ,and in some of them you can simply make do with c#. Another problem might some of those kinda of projects are usually not done in .Net to begin with. It seems that F# is very nice for projects that are more based around calculations and formulas, but that's not enough for it to gain critical mass. Also C# has been encroaching on F# by becoming more functional with things like LINQ, lambdas etc. The type system is worse (C# main weakness right now), but still. I'm no F# expert though so feel free to correct me