Mostly what I have seen happening is people really loving F# convert to using C#. The tooling being the main reason.
What this article isn’t saying is that F# is awful at interoping with C# and windows APIs in general. Mostly that F# functions cannot be used as Func<> objects. So even in a C# environment, bringing some F# is a pain. Definitely didn’t help the adoption.
Yes, it would actually help so much if F# libraries could be painlessly used in C#, it might be all that was needed.
Unfortunately it's not the case.
Maybe if discriminated unions are ever added to C# some real cross compatibility could be made,
Mostly what I have seen happening is people really loving F# convert to using C#. The tooling being the main reason.
What this article isn’t saying is that F# is awful at interoping with C# and windows APIs in general. Mostly that F# functions cannot be used as Func<> objects. So even in a C# environment, bringing some F# is a pain. Definitely didn’t help the adoption.