F# lacks the Visual Studio tooling support that VB.NET, C# and even C++ enjoy.
It is also not officially supported on UWP, and needs some hacks to the generated MSIL (as .NET Native doesn't cover 100% of all MSIL).
It is also not officially supported on UWP, and needs some hacks to the generated MSIL (as .NET Native doesn't cover 100% of all MSIL).
If you attempt to do GUI development, then you are forced to look for community projects like Fabulous, use the XAML type provider with a dummy C#,VB.NET,C++/CLI project for the XAML generation, or actually use one of those languages for the UI, with F# used only for the logic.
So even though I am a big fan of ML language family, at the end of the day, the other .NET languages get the green light from most customers and team.
There's a hope that with F#'s upcoming move to the "shared project system" that a lot of the pains will go away in hopefully the near future.
(That said, Fabulous has piqued my interest and I'm debating rewriting my big F# GUI in it, at least in an exploratory branch.)
For example, try to generate EF 6 Database First code for F#, or use Blend alongside Visual Studio with F#.
> IDE support is much more than just editing text.
In case anyone reading this thread comes away thinking that VS Code + Ionide is only a text editor.