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.
That's a fantastic update! Thanks!
As addendum to my earlier comment, we (a Silicon Valley startup) are only using .NET and Microsoft tools at present _because of_ F#. Were it not for F#, we would likely be a full-stack Python company. F# has a very good chance of reaching into markets where Microsoft and even Java are typically avoided. My only blocker when evangelizing F# to other startups is in the tooling and support. Your reply, while welcome, is a perfect example of why you see such little adoption of F#.
Hi, Clint. I think many of us want .NET Native support for IoT purposes. Many others, including my company, build mobile apps in F# on Xamarin and would like to be able to also support Windows.
F# library support in Windows 8 (PCL) was very weak and had many problems. For the most part, it was easier to port the code to C# than to try to get it to work. Also, given MS did not support F# all the way to the UI layer, you were certain to see very low adoption.
As a better metric, consider the use of F# for building Xamarin applications on iOS and Android. While still a small percentage, I think you'll find it significantly higher than what you saw in the Windows Store. Full support goes a long way to giving you more reliable metrics.