4 ms·
With the exception of UWP support (which I'm sure will come), F#'s future seems pretty certain to me. There seems to have been a lot of interest in it lately, p
by GordonS 9y ago
With the exception of UWP support (which I'm sure will come), F#'s future seems pretty certain to me. There seems to have been a lot of interest in it lately, probably fueled by the current hype over functional programming.
- pjmlp 9y agoCheck the newly released Visual Studio 15.3. https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/ https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... Apparently lack of support wasn't enough to delay Visual Studio 15.3's release, just let the community deal with it.
- GordonS 9y agoPoint taken; it's obviously not a top priority for them, with C# remaining the primary focus. I guess that makes sense, since so many more devs use C#. While dissapointing, I'm sure (well, I hope :) F# support will land in VS before too long. In the mean-time, VS Code really is a great alternative
- TensorMetric 9y agoIt also doesn't help when prominent members of that that community keep spreading FUD about UWP, driving more Windows developers away from F#. https://www.reddit.com/r/programming/comments/6tppt4/f_and_net_core_roadmap_update/ https://www.reddit.com/r/programming/comments/6tppt4/f_and_n... https://twitter.com/k_cieslak/status/896658073338695680 https://twitter.com/k_cieslak/status/896658073338695680 https://twitter.com/k_cieslak/status/896847612766289921 https://twitter.com/k_cieslak/status/896847612766289921 https://twitter.com/k_cieslak/status/897036090489671680 https://twitter.com/k_cieslak/status/897036090489671680
- pjmlp 9y agoFully agree with you regarding that prominent member. Of course he doesn't care about UWP support, as he wants to promote his own VSCode plugin.
- TensorMetric 9y agoAlso sad to see those members who liked his tweets.
- pjmlp 9y agoWe can forget about UWP support, it isn't going to happen in the near future, who knows if it ever will. "The F# team is currently focused on .NET Core tooling in Visual Studio and further support for .NET Core as it evolves. There is no ETA for .NET Native/UWP support at this time." -- Phillip Carter [MSFT] https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net-core-roadmap-update/#comments https://blogs.msdn.microsoft.com/dotnet/2017/08/14/f-and-net... Better focus on C# and C++ and call it a day.
- TensorMetric 9y agoI really can't stand C#. F# is what drove me to .NET in the first place. And I don't like going back to C++, is there any GUI/XAML tooling for it? If not, I'd rather use something like Rust.
- pjmlp 9y agoWith UWP, Visual C++ kind of finally caught up with C++ Builder, it even has support from Blend for UI design. MFC is mostly on maintenance and new application should use XAML + C++/CX. C++/CX makes use of the C++/CLI extensions but it targets AOT compilation to native code instead. The alternatives are C++ with WRL (Windows Runtime Library), basically ATL replacement, and what most Microsoft teams actually use for the UWP kernel components. https://docs.microsoft.com/en-us/cpp/windows/universal-windows-apps-cpp https://docs.microsoft.com/en-us/cpp/windows/universal-windo... Because most C++ devs would rather use something more standards friendly, there is work in progress to eventually replace C++/CX with C++/WinRT, taking advantage of C++17 features. “Embracing Standard C++ for the Windows Runtime" https://www.youtube.com/watch?v=lm4IwfiJ3EU https://www.youtube.com/watch?v=lm4IwfiJ3EU “Putting Coroutines to Work with the Windows Runtime" https://www.youtube.com/watch?v=v0SjumbIips https://www.youtube.com/watch?v=v0SjumbIips