That page is really outdated. It's a good start, lot of things work, lots doesnt. Is for early adopters but it's not bleeding edge anymore i think. Not ready

That page is really outdated. It's a good start, lot of things work, lots doesnt. Is for early adopters but it's not bleeding edge anymore i think. Not ready for production F# using .net core sdk from command line works (new, restore, build, run, test, publish) like c#. xplat is ok where .net core is supported, so osx/ubuntu/win/docker. Docs need some improvements, but lots are language agnostic, or c# examples help (docs are open source, if someone want to help). Important wip or not implemented yet feature of compiler/language: - type providers - portablepdb for enable debugging - f# repl The f# libraries in ecosystem are starting to support .net core (netstandard), like FSharp.Compiler.Services (the compiler as library), Suave ( github.com/SuaveIO/Suave-CoreCLR-sample ), Argu, Fable. These are not hello world examples, so it works. Some are in prerelease, but it's expected because it's a new framework/tooling and need testing. There are only few libraries of the f# ecosystem who support .net core, but it's expected because is a bootstrapping issue in lot of cases (i need to wait .net core support for my dependencies add support..) Obv it's possibile to use all others .net libraries who support .net core (netstandard) like the BCL, Kestrel, etc. As editor, vscode has the best support using usual the amazing Ionide plugin for f# (who already give f# support for .net and mono). Intellisense, build, run is ok but not debugging. Using Visual studio, only build/run works (xproj and project.json), but not intellisense or debugging. If you want to chat there are two good f# slack groups - #dotnetcore in fsharp.org slack (other chan too) - #fsharp in fpchat.com