What are some negative points / cons / bad / limitations about F# (sharp) programming language? [closed]

Question

I would like to know what are some negative points / cons / bad / limitations things about the F# (sharp) language.

I've been searching on google:

• f sharp language limitations
• f sharp language cons
• f sharp language negative points
• f sharp language bad things

And no result about it. This is the reason of asking this here.

The objective of this question is NOT to choose my next language to learn but to make a document for my school about the f# language. But I cannot find any negative points.

Answer 1

• For some people, typically newcomers to the language, the powerful type inference can be offputting
  • It can seem as if the language is dynamic and thus not come with the same guarantees as you expect from a statically typed language. However it's quite to the contrary in reality since F# with its ML heritage is more statically correct than many traditional static languages.
  • Some people find that the lack of type annotations can sometimes make the code less readable - especially if you do not have access to an editor which can highlight the inferred types for you. A good example of this is doing code-reviews or just looking at other peoples code on github.
• Compared to its .NET brethren C# it lacks a lot of tooling. Even simple refactoring doesn't work very well in Visual Studio. Working with GUIs is also not as well supported since you can't work with XAML files the same way you can in C#
• F# lack support for functors, it's not really a huge problem but it's something that people coming from OCaml might miss, for more information see this question.