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.
Does anyone over there care? Do you not understand your own technologies? Truly a drop in talent and passion in this group.
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.
Incredible that users are asking for the obvious, and it still takes over a year to even acknowledge that there is even a problem. Talk about corporate cruft and malfeasance! The GitHub issue has my upvote, and is probably a better place to focus our energies. This place and the UWP group is a joke.
310 votesworking on it · 30 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
So sad that Microsoft and the Windows group used to be full of smart people who cared and were passionate about the technologies they worked on. Now it is a shell of an organization that simply sits on its hands, waiting for a paycheck. Very disappointing to see that this has taken so long, or really to even identify it as a problem in the first place. Clearly an IQ exodus has taken place.
Please get your act together and be competitive like you were back in the day. Other Microsoft groups are running circles around you, and far more transparent!