I do think it depends where you live and what ecosystem's are around there. F# to me fills a niche - i.e. in an ecosystem that uses .NET but is also more tech-s

I do think it depends where you live and what ecosystem's are around there. F# to me fills a niche - i.e. in an ecosystem that uses .NET but is also more tech-savvy and willing to evaluate best tools and new approaches. That intersection of users being small shows a bit about .NET developers culture than the F# language itself (IMO only!). It happens less in the Java ecosystem and I suspect that's because Java was much slower to improve - C# isn't the best language on the platform IMO but it is improving all the time. Often reading a new C# release notes in previous roles (C# 6, 7, 9, 9) felt like reading very old F# release notes which means people don't necessarily have to take the risk to get the language endorsed in their enterprise - they just need to wait and they will eventually get something representing it (if not as generic or ideal as the F# impl). That's more an observation I've seen on the ground in previous roles but YMMV.