But knowing microsoft and looking at the AI commits in F#, (honestly AI could write this stuff faster), I am even willing to accept some bugs if the LSP saw some good improvements regularly.
This is the same issue Haskell has before all the work that went into hls, tbh it's still behind the times but it's on parity with usable tooling.
But man are the F# folks weirdly bad at tooling, fable is good but it's just that nothing in the JS ecosystem even remotely works long term, no ecosystem nor support.
You have to either only use React or hope the library you picked in F# gets ok support somehow, or just vendor it.
For backend F# is much better but only because C# ecosystem offers most libraries you may need. But no one makes F# first/native libraries at all, atleast nothing that keeps being maintained over a longer tail.
I will if F# team @ Microsoft, gets the old or the new wip LSP fixed and improved enough to be modestly good.
But knowing microsoft and looking at the AI commits in F#, (honestly AI could write this stuff faster), I am even willing to accept some bugs if the LSP saw some good improvements regularly.
This is the same issue Haskell has before all the work that went into hls, tbh it's still behind the times but it's on parity with usable tooling.
But man are the F# folks weirdly bad at tooling, fable is good but it's just that nothing in the JS ecosystem even remotely works long term, no ecosystem nor support. You have to either only use React or hope the library you picked in F# gets ok support somehow, or just vendor it.
For backend F# is much better but only because C# ecosystem offers most libraries you may need. But no one makes F# first/native libraries at all, atleast nothing that keeps being maintained over a longer tail.
I tried some game dev in F# but man was it rough.