7 votesAnonymous shared this idea ·
F# team just posted an update on their GitHub. https://github.com/Microsoft/visualfsharp/issues/1096
This is still a work in progress. One key thing from that post is some of these features and fixes have already been underway for months. While we’ve been investigating F#-specific issues in .NET Native, the team has continued to improve .NET Native. One feature known as “universal shared generics” is likely to have improved .NET Native’s support for F#, even without that being an explicit goal of the feature.Anonymous commented
The low number of F# applications as you cite, is a direct result of your lack of tooling support for F#.
Forcing F# developers to have an hybrid application C#/XAML gui + F# portable library means only the more persistent will go that route.
Almost everyone else will give up and go full C#, given the constraints you impose on them.
Microsoft should decide how serious it is with F# and give a clear message.
Even C++ now has better tooling support.Anonymous supported this idea ·