3 ms·
At what point does big company politics become a drag rather than a lift ? F# is not Microsoft's important story in a way that Java was for Sun. In such situat
by srean 9y ago
At what point does big company politics become a drag rather than a lift ? F# is not Microsoft's important story in a way that Java was for Sun.
In such situations, I wonder if something that came into being organically and in the open (and helped on by a sugar daddy) has better chances/purchase.
- pjmlp 9y agoReplacing the contents of my previous post regarding VS 15.3 support of F#. "For long time .NET developers, a common question is "when will Visual Studio support F# .NET Core projects". We’re working hard to get this functionality ready, but unfortunately, we’re not quite happy enough with the quality in the 15.3 update to announce that it’s fully supported. While Visual Studio 2017 version 15.3 is able to open the new F# .NET Core projects, build, and debug them, IntelliSense does not yet work correctly" From 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...
- phillipcarter 9y agoI'm sorry, but what you're saying is factually incorrect. Can you please update your comment so as not to spread misinformation?
- pjmlp 9y agoUpdated with the blog quote.
- phillipcarter 9y agoThis is for the .NET Core tooling support part of F#, and as we've stated in the blog post, we prioritized the quality of cross-platform usage here. You're free to disagree with this prioritization, but please don't craft a narrative about the relationship between F# and Microsoft that can mislead people as you did before.
- pjmlp 9y agoIf the issues faced by your team were related to C# I assume management would have taken other path. And this is the reason why none of our customers wants to even discuss integrating F# into C# projects.
- phillipcarter 9y agoPerhaps it's worth taking a different viewpoint. With VS 2017, no single release updates every part of the product to the latest things. For example, UWP does not support .NET Standard 2.0 yet. That did not put the VS 2017 15.3 release on hold. Similarly, although F# fully supports .NET Core and .NET Standard 2.0 with this release, the tooling quality wasn't high enough for us to declare the associated tooling support in VS as fully supported. That also did not put the VS 2017 15.3 release on hold. This because we're already three updates into Visual Studio, and it's only been 6 months since its release. Visual Studio updates faster and teams can release things easier and more rapidly without needing to wait for everything else. This is a really good thing.
- twodave 9y agoThis, and also VS2017 did in fact ship C# without some things (for instance, full support for value tuples).
- TensorMetric 9y agoThis is minor compared to all the major things VS isn't shipping for many years in a row now.
- pjmlp 9y agoPoint taken, but apparently Microsoft employees keep forgeting F# is part of .NET, or isn't EditorConfig at all relevant for F#? https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-code-style-settings-reference https://docs.microsoft.com/en-us/visualstudio/ide/editorconf...