[aithrowawaycomm]

Sadly I cancelled my Rider subscription this year because AFAICT they've stopped supporting F#, it hasn't worked well for at least two years and has only gotten worse: crawling performance, lots of erroneous red squiggles, no IDE support for later .NET features. Maybe Visual Studio is better than it was a few years ago, but these days I just use emacs, and the MS F# team seems to prefer VSC over VS.

[neonsunset]

This is complete nonsense. Rider has first-class F# support and a sizable faction of employees internally who love and use it.

[aithrowawaycomm]

Do you actually use Rider for F#, or are you just repeating old wisdom? Your comment is rude and unhelpful, because I gave my direct experience as to why I stopped using Rider, and you responded with an empty platitude. Yet you did so in the most thoughtless, dismissive way imaginable, as if I was simply lying.

Rider was first-class a few years ago but has gone badly downhill, and it does not support F# on newer versions of .NET - or at least it didn't in June 2024 when I cancelled my subscription.