Skip to main content
The 2025 Developer Survey results are in. Explore insights into technology and tools, careers, community and more. View results.
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 3
    Flat-out assertion: a language you can learn that fast isn't worth adding to a business development mix. The point in F# is to write functional code, and most people aren't going to learn functional programming that fast.
    – David Thornley
    Commented Dec 29, 2010 at 19:11
  • 8
    Flat-out counter example: LINQ. Writing functional code is absolutely not the point of F#, by either definition of "functional". In the context of existing C# devs, they should already be half way there with System.Func.
    – J D
    Commented Dec 29, 2010 at 20:13
  • 1
    If F# is not primarily about functional programming, then what is it really about? How do you know when F# is a better fit than, say, C#?
    – Robert Harvey
    Commented Jan 3, 2011 at 21:19
  • 5
    @Robert: F# offers a variety of features that can make it much more productive than C#. Variant types and pattern matching are hugely powerful for creating and manipulating trees, which appear in everything from compilers to computer graphics. Type inference makes it easy to write heavily generic code, which is ideal for dense algorithmics. The interactive sessions are ideal for disposable code, like massaging data sets from one form to another or even doing sophisticated analysis. These features are only incidentally related to functional programming and all work well in imperative code.
    – J D
    Commented Jan 5, 2011 at 19:38