I get that, which is why I said it is important for some people depending on the domain and I meant in general language communities. Python is different at least to me given AI and being the first target for not just software improvements but hardware usage (e.g. GPU accelerated specialised libs) and training materials/examples. It is the AI community not the Python community per se; the AI community just targets Python. JS is also a little different given browsers are so ubiquitous and their own target with JS being the main language that works there.

Otherwise in most mainstream platforms there is enough libraries for most things already; which includes .NET. It's rare not to find a well maintained lib for the majority of use cases in general whether it is .NET, Java, Go, etc which is why w.r.t long term risk a used platform is more important than the syntax of a language and its abstractions. Web frameworks, SDK's, DB drivers, etc etc are all there and generally well tested so you won't be stuck if you adopt F#. I evaluate on more objective metrics like performance, platform improvements, compatibility with other software/hardware, etc etc. It isn't that risky to adopt F# IMO (similar risk to .NET in general) - to me its just another syntax/tool in my toolbelt with some extra features than usual if I'm developing things typical in that .NET/Java/Go abstraction level.