It's also worth noting that .NET Core is not only cross platform, but an extremely performant runtime which really hits the ceiling in various benchmarks https://www.techempower.com/benchmarks/#section=data-r17&hw=...
app.Run(async context => { await context.Response.WriteAsync("Hello, World!"); });
Is F# still the red-headed step-child of Core?
Last I fiddled with it F# was looking pretty unloved, but to be fair C# was still having a hard time with Core itself.
Yup. Although this doesn't really come into play with server code in my experience. I don't imagine I'd want to deal with it writing WPF / UWP things though where language support is more important
Even then I might just write the business logic in F# and glue things together with C#
As the article points out, there never has been any visual forms designer type stuff for F#, so if you're writing a GUI app with F#, it's best to wrap it in a C# shell anyway.
Which is fine, because you wanted to separate your core application logic from the GUI anyway, right?
> I might just write the business logic in F# and glue things together with C#
It's a perfectly reasonable way to go.
The only difficulty is that it simplifies things if you don't try to do all the fancy FP stuff at the boundary between the F# and C# parts of the app. While there are ways to pass, say, a tuple from F# to C# and cope with it on the C# side, it's better to limit types at this interface to things both languages support as first-class citizens: arrays, objects, simple scalars, etc.
Is f# a good language to work with in Linux servers? Is possible? Would you recommend it?