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.Some Idiot commented
David & Onur, you are far too kind. UWP group needs a serious flush, and replaced with employees that care about Microsoft and also understand its technologies. This group has checked out and does not show the passion (and competence) other Microsoft groups show, notably Azure and VSO. It certainly feels like a checked-out group that is just collecting a paycheck, waiting for someone to sweep them out, which is exactly what should happen. Even with feedback here on the board it is far too sparse and even with Clint's "checkin" here we are going on a month now without a reply amidst some very intense and thoroughly damning feedback here. Other popular votes are going on over a year now without a response or update. That is not dialogue or customer engagement (which is separates UWP group from other Microsoft groups), that is simply getting by, waiting for anyone with authority to notice -- or care.
It is truly sad to see a technology labeled as ".NET" and it simply not live up to the name. It's almost as if a team of Apple or Google engineers snuck in there and is trying to sabotage this technology for their own benefit. Unfortunately, that is far too complex an explanation of the sad situation that we currently face with this group. Incompetence or corporate malfeasance? You take your pick. Upon reflection we will ultimately have to go with utter incompetence as F# does end up working on Apple and Google platforms, after all. I mean, you can't make this stuff up.
A ".NET" compiler without support for F# -- or any language! -- is like building a car without an engine in it. Sure it looks like a car, and for all intents and purposes it is a car, but one of its defining, powerful aspects that truly make it what it is is absent. It is as if everyone understands Microsoft technology except this group.
F# is not the end of it either. They are guilty with their flagship UWP port as well, trying to copy concepts from WPF and failing miserably. Have you not seen the votes on this board for all the missing functionality in UWP and in particular its Xaml capability? Simply a shell of legacy technologies -- with the adoption rate to prove it.
There is no passion here. Just paychecks and clueless nut-scratching over business and use cases. Also, having to ask "what's the use case for that?" is a sure-fire clue that someone has passed their prime, leaning on organizational dysfunction as dead weight, and should be fired immediately. I hope the right thing is done and a full, comprehensive purge fixes this scourge from Microsoft soon enough.
232 votesSome Idiot commented
Thanks for your feedback, Kai. To be sure, this ask is for tooling around the Extensions API exactly like you suggest in regards to an asm.js/WebAssembly.
This would indeed involve a serious toolchain and development process on .NET's side as you suggest (see: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/10027638-create-a-ubiquitous-net-client-application-develo ), but at some point it would indeed involve integration with the Edge team to properly connect the pieces and have their API play nicely with the new system.
There are two sides to MSFT: web and native (.NET), and they do not have to be incompatible. However, to build a bridge you need two stable foundations on each side from which to anchor the bridge. :)
More than anything, this is asking the Edge team to account for their side of the work (and to build awareness/demand, etc).
The important thing here is that we are NOT asking for another ActiveX/plugin design. Those days are over and done -- thankfully!