6 ms·

I find this to be an interesting cultural phenomenon, this thing where people in .NET-land are skittish about F# because it's not so tightly controlled by Micro

I find this to be an interesting cultural phenomenon, this thing where people in .NET-land are skittish about F# because it's not so tightly controlled by Microsoft. Meanwhile, I'm pretty sure nobody even wants Oracle to be getting involved in Kotlin or Scala or Clojure.

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 ago
  The irony is that F#s releases are in lock-step with the Visual tools team releases and schedule.
  - GiorgioG 7y ago
    I 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 ago
      Perhaps 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.
pjmlp 7y ago
Usually those are the same people that preach OpenJDK, while forgetting that 90% of the contributions come from Oracle. And that Oracle alongside Sun and IBM has been there since the begging, and other than IBM, no one else made an offer to buy Sun. Or if the JVM had died with Sun their languages wouldn't even exist.
mlevental 7y ago
openjdk exists though and is broadly maintained. i don't know how many people use mono (i honestly don't know) but CLR seems to be the only runtime for F#.
thijsvandien 7y ago
I think that F# has a difficult spot in between. Microsoft has enough control over it to effectively kill it (mostly via the ecosystem), but at the same time does not step up and actually "own" it. Since it's still "their" language, anyone considering it would like to see they're still invested in it, which isn't all too obvious at the moment. On the other hand, if they'd distance themselves more, another organization could step up, become the big name behind it, and provide good stewardship. Right now it's just sort of hanging on the side and (at least) outsiders don't know what's going to happen with that, which doesn't inspire much confidence. They just don't seem to care much.

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 ago
The irony is that F#s releases are in lock-step with the Visual tools team releases and schedule.
- GiorgioG 7y ago
  I 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 ago
    Perhaps 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.

pjmlp 7y ago

Usually those are the same people that preach OpenJDK, while forgetting that 90% of the contributions come from Oracle. And that Oracle alongside Sun and IBM has been there since the begging, and other than IBM, no one else made an offer to buy Sun. Or if the JVM had died with Sun their languages wouldn't even exist.

mlevental 7y ago

openjdk exists though and is broadly maintained. i don't know how many people use mono (i honestly don't know) but CLR seems to be the only runtime for F#.

thijsvandien 7y ago

I think that F# has a difficult spot in between. Microsoft has enough control over it to effectively kill it (mostly via the ecosystem), but at the same time does not step up and actually "own" it. Since it's still "their" language, anyone considering it would like to see they're still invested in it, which isn't all too obvious at the moment. On the other hand, if they'd distance themselves more, another organization could step up, become the big name behind it, and provide good stewardship. Right now it's just sort of hanging on the side and (at least) outsiders don't know what's going to happen with that, which doesn't inspire much confidence. They just don't seem to care much.