4 ms·

F# is even less used than OCaml and Microsoft lost interest in it. If you are into functional programming, you should rather choose Scala. Huge ecosystem, larg

F# is even less used than OCaml and Microsoft lost interest in it. If you are into functional programming, you should rather choose Scala. Huge ecosystem, largely used in production. Compatibility with java mean you can have all the library you want. A lot of people love to trash sbt it's build system, but for me it always work as expected. And other tooling are just awesome (you even have IDE).

suprfnk 9y ago
> Microsoft lost interest in it. Do you have any sources for this?
- bonesss 9y ago
  F# clearly lags behind C# in editor attention and integration into the latest and greatest GUI techs from Microsoft... For many on the MS treadmill this is seen as a negative, as you can't always get visual studio RCs and be months ahead of the competition on the next version of blend/WPF/silverlight/whatever. For others, the community driven aspect and lack of obsessions with technical fashion in the MS product line (with the track record they have...), is seen as a _major_ feature. F# has a much more active open source community and presence than C#, most of the devs are actively cross-platform in a way C# still struggles with, and it has a better .net stack than C# aimed at command line efficiency and relatively stable approaches to common problems. F# is still a first class language from MS, and would be quite OK on its own these days. Regardless, there is no chance MS will "lose interest" in F# given the impact on data science, machine learning, cloud computing, parallel computing, and stream-processing F# has. MS invested heavily in filling out their language portfolio to avoid being excluded from the big servers and big clusters. Time has shown those concerns to be growing, not shrinking :)
lenkite 9y ago
According to members of the .net team, one should embrace f#: https://blogs.msdn.microsoft.com/dotnet/2017/05/31/why-you-should-use-f/ https://blogs.msdn.microsoft.com/dotnet/2017/05/31/why-you-s...

suprfnk 9y ago

> Microsoft lost interest in it. Do you have any sources for this?

bonesss 9y ago
F# clearly lags behind C# in editor attention and integration into the latest and greatest GUI techs from Microsoft... For many on the MS treadmill this is seen as a negative, as you can't always get visual studio RCs and be months ahead of the competition on the next version of blend/WPF/silverlight/whatever. For others, the community driven aspect and lack of obsessions with technical fashion in the MS product line (with the track record they have...), is seen as a _major_ feature. F# has a much more active open source community and presence than C#, most of the devs are actively cross-platform in a way C# still struggles with, and it has a better .net stack than C# aimed at command line efficiency and relatively stable approaches to common problems. F# is still a first class language from MS, and would be quite OK on its own these days. Regardless, there is no chance MS will "lose interest" in F# given the impact on data science, machine learning, cloud computing, parallel computing, and stream-processing F# has. MS invested heavily in filling out their language portfolio to avoid being excluded from the big servers and big clusters. Time has shown those concerns to be growing, not shrinking :)

lenkite 9y ago

According to members of the .net team, one should embrace f#: https://blogs.msdn.microsoft.com/dotnet/2017/05/31/why-you-should-use-f/ https://blogs.msdn.microsoft.com/dotnet/2017/05/31/why-you-s...