In tooling, books, conferences, critical applications used in large scale across the industry.
Meanwhile Microsoft keeps behaving as if it was a management mistake to have added it to VS 2010.
I encourage you to look at the state of Clojure and its usability within larger Java ecosystem. Quantity of material, as usual, is not everything.
> Meanwhile Microsoft keeps behaving as if it was a management mistake to have added it to VS 2010.
Do you have anything to back up this assumption with?
Scala still powers a lot of big data and distributed computing frameworks in Java ecosystem. In .NET, the counterparts which only exist for Akka really, are written in C#.
.NET has hardly any big product that is relevant for big data folks, and the ones that exist are equally written in C#.
The only well known flagship product was JET.com, meanwhile acquired by Walmart, which by now was rewriten most of it.
The lack of exposure in .NET ecosystem, not keeping to the story how to sell F#, first companion class libraries, then Web development, maybe type provideders with the World Bank example demoed to exhaustion, maybe machine learning (while Microsoft actually hires Guido and alongside Facebook brings performance improvements and JIT support), only C# and VB are default for Windows desktop workloads, nowadays in what concerns .NET 9, who knows what the theme is.
In Visual Studio 2024 full installation, how many C# workloads also support F# as an option?
It is basically CLI, class libraries, and those old Web projects from the "F# is great for Web" marketing phase.
There are other companies which use F# in the area of logistics, pharma and I know of at least one company that has services in it in a bit less reputable industry.
I feel like this kind of perception is highly biased, or, at least, unhelpful.
For what it's worth, I have been a newcomer to both languages the past few years. Clojure has been way more usable than F# and it's not even close.
Clojure is firmly in the quality not quantity category. Good books, novel libraries, a very active slack. Things usually "just work."
F#? Broken type providers, scaffolding that doesn't work past .NET 6.0, a genuine lack of books. Sometimes things work great, they often don't, and the typed nature makes a lot of these things hurt more.
