Krzysztof Cieslak

The fact that Rider is using FCS for #fsharp support means that we shouldn't expect much better quality and more features than what exists in currently existing tooling (Ionide / XS). Tho, it will be probably more stable.

Actually I expect the support to be pretty minimal - they don't really want to invest into F# ecosystem, but just support mix language solutions. Open sourcing it is also interesting - someone is hoping that Community will build more advanced support, I guess

Apr 21, 2017 at 11:56amWeb
Show threadAdam GuestApr 21, 2017
@k_cieslak I for one, was planning on keeping code/ionide as my preferred f# environment. And given how resource hungry R# is and how well ionide ran while my pc was running like shit, I really can't think of a compelling reason to change.
Show thread7sharp9Apr 23, 2017
@chamook @k_cieslak All I really want is a way of opening the F# compiler project and have some tooling that works. XS struggles and quickly eats 9GB ram, ionide takes a nap. Debugging ionide with FSAC is a bit of a pain to see what the issue is.