3 ms·
> this thing where people in .NET-land are skittish about F# because it's not so tightly controlled by Microsoft. Microsoft's great tooling is what has made (t
by GiorgioG 7y ago
> this thing where people in .NET-land are skittish about F# because it's not so tightly controlled by Microsoft.
Microsoft's great tooling is what has made (traditionally) it sticky for a lot of developers. F#'s tooling from Microsoft has been a half-hearted effort (organizationally, not speaking of the effort that the F# guys have put in.)
- Rapzid 7y agoThe irony is that F#s releases are in lock-step with the Visual tools team releases and schedule.
- GiorgioG 7y agoI must vehemently disagree. From: https://github.com/dotnet/fsharp/issues/2400 https://github.com/dotnet/fsharp/issues/2400 "GiorgioG commented on Oct 19, 2017 @masaeedu - Not to beat a dead horse, but we've been waiting for an RTM release of this since May when VS2017 first RTM'd. We were then told it would likely come in the July release of VS, we're now nearing the tail end of October with no clear idea when we'll get it. It's not @cartermp 's fault, just the reality that MS has not made it a high priority (judging by their actions, not their words.) In summary, if you want to use F#, use VSCode, it has excellent support for F#, as long as you realize it's not Visual Studio, it's a souped up text editor."
- Rapzid 7y agoPerhaps it's not the case anymore, but I meant more that F# language releases used to be delayed until the Visual Tools team was ready to release a new Version for Visual Studio. So essentially, the F# releases seemed to be held up. Perhaps I'm remembering wrong and/or this has changed since the .Net core support came in.