41–43 of 43 posts
I just started learning F# with the help of a well known F# dev. It's been a fun challenge. Give yourself the chance to try it out. Do check out http://fsharpforfunandprofit.com Its a great resource.
I worked through quite a few of the exercises on http://exercism.io/ and can recommend the challenge and the community around it for learning by writing code.
Earlier quoted context omitted.
fsharp would really take off if it had a framework as attractive as phoenix.
I've thought about this too, and unfortunately it is not feasible, because of the poor/nonexistent meta programming support in F#. Phoenix uses macros for optimizing functions from templates at compile time, handling translations in a clean way, and removing a lot of boilerplate. Source: Have spent a lot of time with F#, including writing Type Providers (which would not solve the problem).
Anyway, I don't think to be "attractive" it needs to match Phoenix/elixir macros. Nice frameworks can be made in fsharp, and its type system and tooling blows type specs and dialyzer out of the water.
Really it needs to be:
* (x-platform && easy to use) which is why I'm so keen for the official 4.1 fsharp release. The ecosystem around fsharp and dotnet core needs all the sharp edges ground down.
* Smooth OOTB experience
* Community momentum
* Excellent plug/middleware solution(building on top of asp.net core might be the right approach)
Then just let fsharp shine on its own merits.
Earlier quoted context omitted.
Fsharp 4.1 does not appear to be released yet. The download for windows is still 4.0. Last I looked ionide did not support .net core. I'm betting it will be released as part of the VS 2017 visualfsharp update. They just called for help testing RC3. I'm looking forward to the release and the subsequent smoothing of the .net core fhsarp ecosystem.
A few things still need to be ironed up. Expect full support around .NET Core 2.0 time. https://github.com/Microsoft/visualfsharp/issues/2400
* Seemless x-platform with dotnet core
* ionide working with dotnet core(and ideally on par with at least xamarin fsharp support)