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.
Did anyone bother to read the language used in the GitHub issue? It reads like "yes, we're committed to F#, but not THAT committed." This is an embarrassment! A travesty! How do you design a .NET technology but do not support .NET languages? You know where F# works? It works in WPF, and even Xamarin allows you to use it. You can even use it to make a console application. A CONSOLE APPLICATION!!!
Why even bother calling UWP ".NET"? That is probably the worst mistake out of all of this. If this wasn't labelled as .NET, then no one would expect the .NET qualities that makes .NET so great. Well, great outside of the twisted, messed up, upside-down cluster that is the UWP group, which definitely has its own version of what .NET is supposed to be, and has failed terribly in making it happen, both in implementation and adoption.
Everyone is truly hoping for an outside group to clear out this cruft known as UWP group and bring back our .NET the way we enjoyed before the clowns took over.
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.
Truly a disgrace to see how watered-down and incompetent the Xaml systems have become. WPF and Silverlight are still so much better, and if we could get away with still using them, we would. We are instead held ******* by these very limited subsets of Xaml. Might as well be using JSON! I am in agreement with others that the GitHub vote is probably the better way to go. It takes years before this group can even decide on something, nevermind actually doing something about it.
310 votesworking on it · 30 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
WPF and Silverlight are still better technologies five years after the fact. They don't use these strange, magic string tokens like UWP that sort-of, kind-of masquerade like markup extensions. These markup extensions feel like a team of outsourced, junior developers made them -- basically having absolutely no clue about what .NET is and getting paid to act like it.
Nope, WPF and Silverlight use real, live markup extensions, the way God intended!!! Also, System.Xaml can be used in all scenarios, not just the under-featured client-tier that UWP has cobbled together. It would be nice to see a separate assembly that can be used outside of clients, but somehow think the outsourced and low-quality culture there won't even consider it.
Seriously, does anyone over there actually do any work?!?! It's been five years since Silverlight and 1.5 years since this vote was put together!!!
Everything is open source in Microsoft now with the exception of this technology, which barely works and nominally adopted. This group is truly an embarrassment to the rest of Microsoft!