Re F# tooling and IDEs: sadly the churn around the transition to .Net Core has really hurt F#s tools. Things that were stable and working since inception, and enabled highly productive workflows, have been trampled by missing features and shifting boundaries on the new platform.
That said: it seems it's finally coming around, as .Net Core matures and gets more mature secondary tooling, a lot of the little blocking issues can finally be addressed.
Re:Why Use F#?
by noobdevguy6335 on Wednesday December 12, 2018 @11:00PM
(#18669760)
I am new to programming...wanted to import and process tables from https://en.m.wikipedia.org/wiki/Megacity
Was using ionide on vscode But not working because .NET CORE is not supported
Returns the suggestion to switch Fsac.Runtime to netcore after I get the error fs0039 HtmlProvider is not defined even though Intellisense recognises it..
...refer below
Re:Why Use F#?
by arwhatever on Thursday December 13, 2018 @03:11PM
(#18675583)
I strongly recommend giving Rider a try for F# development - I've been really impressed.
I bounce between Scala and Kotlin. But as a Linux dev I find the JVM far more forgiving.