4 ms·

There are a few reasons why I use it on Linux over OCaml. 1) Familiarity, if you already know the language, tooling and libraries then you might be better off

There are a few reasons why I use it on Linux over OCaml. 1) Familiarity, if you already know the language, tooling and libraries then you might be better off sticking F# than learning OCaml. 2) Size of community. I'm willing to be proved wrong here, but I find it alot easier to get an F# question, and often more importantly, a question about a library I'm using when I write F# than when I write OCaml. 3) Libraries, Libraries, libraries... Also the mono runtime is pretty darn good. I agree its not as tuned to handle the small object and lifetimes that functional languages generate but I'm not really running into that limit currently.

enricosada 13y ago
About libraries, .NET has a big, complete and really good documented standard library. With standard library I mean int/float/string/IO/http/xml/async/etc not speaking about stacks of .net (like ui with wpf). Standard library work really good cross platform with mono, share documentation/stackoverflow with .NET. Mono team fix fast bug when behaviour differ from .NET Instead of use complex stack like wcf (to create service, partially implemented on mono, webservice ok, soap WS-* less) but bundled with .NET, you can use open source libraries (like nancy, servicestack), change serialization library, etc. F# use .NET standard library (same library/dll, so a c# answer about StringBuilder class is the same from c# and f#). Can also use every .NET library, bundled with mono/.NET or third party.