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.
Seen recently from the redirected thread above:
"the ability to use F# in a UWP app likely won't be available for some time."
I've seen some people joke on here and on a few blogs now that this group does nothing but play Halo all day. While funny, I am starting to think there is some merit to it. I am in agreement with others posting here. This very popular idea has been on the books for over a year now, and it sounds like there is at least as much work left or more to do on it -- that is, if there is actually anyone over there that does any work!
It is quite clear the UWP group doesn't understand .NET and the fact that one of its premiere languages has not made it to its quite mediocre platform that no one has adopted is simply unacceptable. The only thing more shocking is that those who continue to butcher the vision of .NET are still employed and continue to make a paycheck doing it.
UWP and the "brains" behind it is truly the worst thing to happen to Microsoft since Clippy and Sinofsky. Sinofsky, incidentally, made Clippy and actually admitted to it. Microsoft actually did the right thing here for once and dumped him once that admission was made. So there is hope!!
Maybe it's time to start poaching back the quality engineers who all flocked to Google, or at least consider being like the rest of Microsoft these days and make this project open source!!!
Or MAYBE require some of the UWP "engineers" to get their heads out of their video games and take a few Pluralsight courses on .NET. The incompetence here is truly staggering!!
232 votes11 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
This is great feedback. We are excited about the Xamarin acquisition and the .NET ecosystem around cross-platform apps. We are currently looking at this and similar feedback on how we can improve the experience of working with both Xamarin.Forms and UWP implementations of XAML.
Agreed with the others, you are better off voting for the GitHub issue, which at this point nearly has as many reactions as this vote alone. This group is responsible for taking something that worked very well in WPF and Silverlight, and then has actively spent the past decade ensuring a subpar, mediocre replacement. I wouldn't be surprised to learn that management over there used to work for Google or Apple, and are guilty of corporate sabotage. How anyone over there has managed to continue getting paid during all this time of doing essentially nothing is indeed a mystery, and something shareholders and press should inquire.
Cannot agree enough with all the other developers here. Seems like the only people who know Microsoft tech are those who don't work there. Truly an embarrassing time for this company and this group in particular. Get your act together, Microsoft!!!