See https://github.com/dotnet/netcorecli-fsc/wiki/.NET-Core-SDK-... for quickstart and info for F# on .NET Core.

VSCode (with ionide), vim (vim-fsharp binding), emacs (fsharp-mode) already support it, with full intellisene. VSCode also support debugging.

About the aspnet stack, same future limitation of C#, as discussed on the post. But there are also alternative web stack, like Suave.

Thanks, I'm aware of that as a resource.

That isn't the issue, the issue is that when I play with things I restrict myself to playing with things that I can potentially use in production at some point, I don't have a lot of 'play time' so it makes sense to prioritise things that have a potential return.

I've played around with it. It works.

.NET Core is totally fine for playing around or for small apps and services.

It's usually for large projects that these backwards compatibility issues tend to crop up and be show-stoppers. You're likely better off with Mono in that case.

We've built our entire backend on .NET Core. We've got a lot of moving parts. The main pain points have ironically been certain Azure libraries which haven't been ported to the standard yet. I've also been using F# core and while the experience isn't yet there, it feels close.