[megaman22]

C# does keep getting better, and making the delta between what it offers and what F# offers smaller, at least from what I can see. I've really wanted to get on the F# train, but I just haven't been able to get it out of the station yet.

I'm somewhat astounded that VB.Net is still a thing, however.

[pjmlp]

F# always suffered from lack of VS tooling support, I was always on the edge waiting for it to be supported on GUI designers just like VB.NET and C#.

Using it mostly for scripting like tasks only.

Then it wasn't relevant for .NET Native support, and finally Microsoft keeps ignoring some vocal anti-MS/C# members in the community, which made me loose any remaining interest.

I rather have C# with some FP like features, than a FP language without tooling support and needless forum discussions.

Regarding VB.NET, it is used quite a lot in some enterprise shops.

I have seen many apps that started as office macros and eventually grew up to be VB.NET ones.

Even if VB.NET is more complex than VB was, it still easier than C# for those office employees that know one or two things about coding.