4 ms·
I've read on HN that F# doesn't get nearly as much attention and support from Microsoft as C# does, to the point where people expressed concern that F# might be
by smt88 8y ago
I've read on HN that F# doesn't get nearly as much attention and support from Microsoft as C# does, to the point where people expressed concern that F# might be put into maintenance mode.
Does anyone reading this feel that way, or was it just FUD?
- xvilka 8y agoThere is always an option to switch to OCaml instead. Especially these days it gets more and more attention to improve Windows support.
- lenkite 8y agoF# support always lags behind by a couple of years. Only very recently (as of last week) you could release F# UWP apps. https://github.com/dotnet/corert/issues/6055 https://github.com/dotnet/corert/issues/6055
- pjmlp 8y agoWhich still isn't production ready it seems. "One thing I noticed is that the compiler only crashes when building x86. It compiles fine for x64." "Are we stuck on "Allowed but not officially supported" for now or are there any plans towards "Officially supported" ?"
- pjmlp 8y agoSpeaking for the tooling attention that is accurate. Somehow F# isn't part of the full .NET team, as such it doesn't get the same attention regarding UI designers (Forms, WPF, UWP), database designers (EF) or deployment targets (IoT Core/.NET Native). There was a Visual Studio release where they decided not to hold back the release, even though it broke a couple of F# tooling. So there is that, on the other hand Microsoft seems to at least be willing to push it as a data science language on Azure.
- oaiey 8y agoMS' Matt Torgeson explained that once. Their investment is aligned with the user base. There are millions C# devs, 100 Thousands of VB.NET devs and 10 Thousands F# devs. But in difference to VB, F# has a independent community with a strong focus on improving F#. All I hear from MS is that they love F# but the workhorse is C#.