Why F#?

As far as I can tell F# is one of those things where every single user is extremely happy. This happens rarely and I really am curious about the thing but never had time to get into it. I'm also pretty well versed in the .net ecosystem so it's probably gonna be easy.

Any tips? What kind of workflows might benefit the most if I were to incorporate it (to learn..)?

The funny thing is that you can write very similar code in C#, so maybe you don't need to switch which language you're using as a CLR frontend.

    using System.Linq;
    using System;

    var names = new string[] {"Peter", "Julia", "Xi" };
    names.Select(name => $"Hello, {name}").ToList().ForEach(greeting =>   Console.WriteLine($"{greeting}! Enjoy your C#"));

LINQ is such a good library that I miss it in other languages. The Java stream equivalent just doesn't feel as fluent.

Modern C# collection expressions make the definition of names closer to F#:

  string[] names = ["Peter", "Julia", "Xi"];

I know working on "natural type" of collections is something the C# team is working on, so it feels possible in the future that you'll be able to do this:

  var names = ["Peter", "Julia", "Xi"];

Which I think would then allow:

  ["Peter", "Julia", "Xi"].Select(name => $"Hello, {name}").ToList().ForEach(greeting =>   Console.WriteLine($"{greeting}! Enjoy your C#"));