I use the 'code-first approach' most the time which really leans into the performance improvements. I can write C# data models that automatically update the database schemas on the SQL side. This is obviously possible in other languages/runtimes, .NET just feels quicker to me once you get it all down and gives you more ways to solve problems than most other languages.
Check it out yourself.
“Can the F# ecosystem survive losing the support of Microsoft?” Is not the kind of question that can be answered by looking at a GitHub repo.
The purpose of this website is conversion, particularly with experts. Asking a question shouldn’t be met with pithy links that don’t answer the question.
F# has been a first-class language in .NET for at least 15 years and has lived on under Ballmer and Satya. It seems to serve as a useful R&D program for both the runtime's capabilities and for features that may go into C#, which will be the premiere language barring a cataclysm. I don't think it's quite as precarious as it might seem on the surface.
The real risk would be not dropping it up but instead giving a slow death by drip feeding support or somehow filling it with ads.