Reflecting on F# in 2017
medium.com
medium.com
It wasn't a training video, much more of a fun coder-to-coder week where Bob and I went through a few sample problems. I tried to show him how thinking in F# is different from the C#/Java most of his viewers are familiar with. I also tried to share some of my excitement with where the language is and how cool it is to have fun coding again.
You can see more about this on the F# reddit group. There's a post where I asked the community what to go over [1], and a post detailing how things went [2].
1. https://www.reddit.com/r/fsharp/comments/7i7ssp/tips_for_int...
2. https://www.reddit.com/r/fsharp/comments/7k3chx/update_on_th...
How does this compare with native Visual Studio on a PC? My impression that you’d be a lot more productive in Visual Studio: https://www.visualstudio.com/en-us/news/releasenotes/vs2017-...
I‘m using F# for some parts of a larger mobile app with Xamarin, and therefore have all three IDEs in use: VS for Mac, Rider, VS Code with Ionide. The ladder feels most lightweight for F# only. In a mixed solution with C# Rider probably provides the best experience at the moment. VS for Mac is not very usable, to put it friendly.
However, tooling is evolving but compared to other platforms not very mature yet. Refactoring for example feels like what most editors support for JavaScript.
But it’s not a show-stopper (for me).
For those of you who don't know F# type providers, check them out, they really are amazing. Providing type inference from HTML web sites, json payloads, SQL Databases amongst others.