David Neale

My feedback

  1. 874 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    92 comments  ·  Universal Windows Platform » Framework  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    David Neale commented  · 

    Thanks for the update Clint. Now we can get back to developing great things in a great language :-)

    David Neale commented  · 

    Anonymous - Microsoft no longer has choice of dropping F#, it's all open source, including all the visual studio integration, so don't worry about that. We just need them to make C# Native into .net Native as they have named it, or allow UWP apps to just run using the regular CLR with JIT. There is plenty of use for F# outside of store apps of course, I'm using it for backend services and desktop applications, it's also great for web development and work is under way to have it running on the CoreCLR as well. So don't be afraid!

    David Neale commented  · 

    Clint, Thank you for the response and further question!

    I think other commenters have hit the nail on the head here, Windows 8.1 apps was not where we wanted to be making apps, so of course there was low usage. But since then F# has been gaining far more interest (functional in general, look at Apple with Swift for instance). Now you have a platform where people would be wanting to write LOB apps for instance, something nobody would have wanted to do before as you would have had to make them publically available, Now we have an increasing number of people moving to F# because of the benefits in terms of productivity and reduction in bugs etc. Now you have a platform (Windows 10) where the adoption rate will be high because you've got it right this time, so now there will be more of us interested in making apps.

    And at this point, you have just put up a road block that says we have to give up and go back to C#.

    You could at least allow UWP apps to not use .net native, and fallback to using the .net JIT again. Otherwise you are sabotaging one of the best things you've created in recent years! Just when the adoption of F# is finally happening! It always takes years for radical new things to take off, blocking it like this seems short sighted.

    David Neale commented  · 

    F# generated assemblies really need to be fully supported, not just PCLs. Functional coding is very much the up and coming way to build all kinds of software and the single biggest market is going to be UWP apps across all device types so we really shouldn't be forced back to imperative coding for those, when we can make higher quality apps (less bugs, better use of multiple cores etc.) using F#.

    David Neale supported this idea  · 

Feedback and Knowledge Base