4 ms·

What was the error? Also like the others say, F# on dotnet is like Groovy for the JVM. It's nowhere near the popularity. Any reason you didn't try C# instead?

xbar 6y ago
It seems like you understand the story for both of them. Any reason why F# is not a valid starting point language on Mac?
- oblio 6y ago
  Because it's a community language. Microsoft doesn't officially support it fully. So you have 20-30 or however many volunteer devs (probably fewer) working on it in their spare time. If you're just getting used to the platform, you're shooting yourself in the foot by going with niche setups. Try C# first to figure out your way around the platform and then branch out, not the other way around.
  - nojito 6y ago
    >Microsoft doesn't officially support it fully. Nonsense all you have to do is install the dotnet sdk and run a single line in your terminal. dotnet new console -lang "F#" -o "project"
    - oblio 6y ago
      Yeah, it's also included in VS classic, if you want to get super fancy. Does it get the same level of support as C#? Hardly. Do bugs get fixed as fast? Maybe. I think there was a Microsoft article that summed it up nicely: there are millions of C# developers (ergo the focus), tens of thousands if not low hundreds of thousands of VB.Net developers (ergo the life support) and maybe hundreds or low thousands of F# developers (ergo the fact that Microsoft offers some integration points but expects the already small community to develop and polish the actual implementation). It took F# several years to fully get supported on .NET Core (type providers and such). I know, because I was watching the Github issue for it for at least 2 years).
- Multicomp 6y ago
  It's valid, just clunky to get going the first time. F# dev team is only ~7 people at MS, the rest is community supported projects and github issues. So while F# devs measure in the 10,000s, C# devs measure in the 100,000s
- phillipcarter 6y ago
  It is. The OP was likely confused with a tool or had a specialized use case tied to Windows that they're not communicating. All the official guides for getting started work. Using specialized tools or components meant for Windows development (e.g., Type Providers not ported to support .NET Core)on a different OS may not work so well.

xbar 6y ago

It seems like you understand the story for both of them. Any reason why F# is not a valid starting point language on Mac?

oblio 6y ago
Because it's a community language. Microsoft doesn't officially support it fully. So you have 20-30 or however many volunteer devs (probably fewer) working on it in their spare time. If you're just getting used to the platform, you're shooting yourself in the foot by going with niche setups. Try C# first to figure out your way around the platform and then branch out, not the other way around.
- nojito 6y ago
  >Microsoft doesn't officially support it fully. Nonsense all you have to do is install the dotnet sdk and run a single line in your terminal. dotnet new console -lang "F#" -o "project"
  - oblio 6y ago
    Yeah, it's also included in VS classic, if you want to get super fancy. Does it get the same level of support as C#? Hardly. Do bugs get fixed as fast? Maybe. I think there was a Microsoft article that summed it up nicely: there are millions of C# developers (ergo the focus), tens of thousands if not low hundreds of thousands of VB.Net developers (ergo the life support) and maybe hundreds or low thousands of F# developers (ergo the fact that Microsoft offers some integration points but expects the already small community to develop and polish the actual implementation). It took F# several years to fully get supported on .NET Core (type providers and such). I know, because I was watching the Github issue for it for at least 2 years).
Multicomp 6y ago
It's valid, just clunky to get going the first time. F# dev team is only ~7 people at MS, the rest is community supported projects and github issues. So while F# devs measure in the 10,000s, C# devs measure in the 100,000s
phillipcarter 6y ago
It is. The OP was likely confused with a tool or had a specialized use case tied to Windows that they're not communicating. All the official guides for getting started work. Using specialized tools or components meant for Windows development (e.g., Type Providers not ported to support .NET Core)on a different OS may not work so well.