Records, tuples, pattern matching, immutability, error handling with Result<‘a>, distaste for nulls, it’s got everything that Microsoft is trying to shoehorn into C# today, without all the baggage that C# brings with it. It seems like F# (fortunately) does have many reasons /to/ change.
Agreed - the tooling and advocacy needs changing. How many times has VS shipped with broken F# functionality.
Kudos to Don Syme for not getting the language too bloated btw, it's hard to imagine it is almost 20 years old.