4 ms·

F# is one of my favorite languages! I'd recommend to everybody to try to learn it. But I kind of don't like the .NET ecosystem, it seems constantly changing bu

F# is one of my favorite languages! I'd recommend to everybody to try to learn it. But I kind of don't like the .NET ecosystem, it seems constantly changing but also at the same time incredibly stable? I can't really explain it well, but I hope F# learning resources not only focus on introducing FP concepts extremely well(which they really do!), but also learn how to deal with .NETisms. Some things I didn't get and felt like I had to shift through C# tutorials/resources to understand: - What exactly is a solution? Is a solution just a bunch of fsproj's en csproj's together? - What is an .NET Runtime assembly? - Do I use NuGet or Paket? Paket seems to be the most recommended, but apparently NuGet has caught up? Now a lot of these questions are trivial, but I felt like that the docs teach you really well the simplicity, power and awesomeness of F#, but they don't really tell you how to deal with the beast that is .NET There have been a lot of awesome resources that do teach you these things, and I'm looking forward to seeing more of it from the sweet F# community. F# 6 seems like another step in the right direction!

CSMR 5y ago
Dotnet is ultra simple and a big advantage of F#. You do need to learn what a solution is: it's a group of projects with dependencies between the projects. Download an IDE, create a new project (which will also create a solution), and go to Nuget in the IDE if you need to install packages. You don't need to know what an assembly is. Some devs like to do things the hard way with a very manual approach, including working with command lines and using paket, and that does give some confusions in the docs since there isn't a clear default path.
- sp33der89 5y ago
  Oh, don't get me wrong, I definitely think dotnet is an advantage for F#, but when I learned F#, a lot of beginner resources didn't teach you how it dotnet works. I think it got easier from .NET Core 3 onwards tho.
- nsonha 5y ago
  > a big advantage of F# I think it gives a (unfair) stigma to an otherwise really nice language
phillipcarter 5y ago
This doesn't necessarily explain the .NET concepts, but there is a walkthrough that shows you how to structure a .NET project with F# here: https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-command-line https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/g... While stuff isn't called out explicitly, it does at least show via example the relationship between projects, solutions, references, and CLI commands.

CSMR 5y ago

Dotnet is ultra simple and a big advantage of F#. You do need to learn what a solution is: it's a group of projects with dependencies between the projects. Download an IDE, create a new project (which will also create a solution), and go to Nuget in the IDE if you need to install packages. You don't need to know what an assembly is. Some devs like to do things the hard way with a very manual approach, including working with command lines and using paket, and that does give some confusions in the docs since there isn't a clear default path.

sp33der89 5y ago
Oh, don't get me wrong, I definitely think dotnet is an advantage for F#, but when I learned F#, a lot of beginner resources didn't teach you how it dotnet works. I think it got easier from .NET Core 3 onwards tho.
nsonha 5y ago
> a big advantage of F# I think it gives a (unfair) stigma to an otherwise really nice language

phillipcarter 5y ago

This doesn't necessarily explain the .NET concepts, but there is a walkthrough that shows you how to structure a .NET project with F# here: https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-command-line https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/g... While stuff isn't called out explicitly, it does at least show via example the relationship between projects, solutions, references, and CLI commands.