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.
+1 to the sentiments expressed in here. This used to be one of the greatest groups in Microsoft, and now it is simply an embarrassment. We are pushing nearly a decade now with the same mediocre featureset with no passion or desire for improvement. Not supporting a .NET language in a .NET technology offering is the cherry topping on the cake of fail. Taking years to pacify angry developers with empty words in the meantime is a despicable achievement.
The good news is that it looks like they are finally wisening up to all the dead weight that is wasting space there. Hopefully they are prudent and hit everyone responsible in the Windows Group for this disaster:
Make Microsoft Great Again!
Agreed with the sentiments. Truly backward group that is clearly holding back Microsoft. It takes years for the simplest and most obvious features to even get recognized. How is anyone over there still collecting a paycheck?! I voted but this idea is a lost cause. This group doesn't care and should be replaced immediately by leadership in either the Visual Studio, Azure or .NET groups. They are far more transparent, agile, and competent than this group, which seems actively deployed to operate against the success of Microsoft!!!
230 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.
GitHub issue has over 100 reactions, by far and away the most popular and active request in that repo! If you don't listen to your developers, why even bother having a voting site?!
299 votes25 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Currently being spec’ed out.
Echoing the sentiments here. Why has this taken so long? Xaml system in UWP is a terrible joke and is not even close to older systems. String values are passed back and forth between COM and it is a mess to work with!!! Might as well code it all by hand and ditch the designer altogether. I also too agree with making this open source and cross platform so that all .NET applications can use it for the powerful serialization engine it is, not the UI cluster it has become in UWP, which was clearly written by a team of interns.
The GitHub vote below says it all. It is overwhelmingly the most popular vote in that repo. LISTEN TO YOUR DEVELOPERS!!!