Why you should learn F#

Post by daxfohl » Tue, Dec 18, 2018, 9:14 PM UTC

dvlsg wrote: post #62

jadbox wrote: post #42

Earlier quoted context omitted.

It sounds like your (more or less) just using classes for just namespacing functions and allowing bundles of functions to get brought in?

I've definitely structured f# modules that way. The module exposes one function that "injects" the dependency into multiple other functions, and then returns them as a blob. I'm not sure if that's "the fsharp way" (i suspect it isn't) and maybe I'll look back on it some day and cringe, but it's working pretty well for some of my (admittedly small) side projects I'm tinkering with right now.

Post by Dn_Ab » Tue, Dec 18, 2018, 9:17 PM UTC

ken wrote: post #45

"No matter if you are already a functional developer from a different community (Haskell, Clojure, Scala, etc.) or you are a complete newbie to functional programming (like I was 3 years ago) I think F# can equally impress you" -> "For this task and for the rest of this blog post I'll be comparing F# with C# in order to show some of the benefits." F# is neat, and I see why it's useful if you have a big .NET program a…

Post by cgrealy » Tue, Dec 18, 2018, 9:22 PM UTC

dustinmoris wrote: post #68

cgrealy wrote: post #55

While I really like the concept of functional programming and F# is definitely on my list of practical useful languages to learn, this article is clearly written by someone who doesn't know C# very well. Take the "To hell with interfaces" example. public interface ISortAlgorithm { List Sort(List values); } public class QuickSort : ISortAlgorithm { public List Sort(List values) { // Do QuickSort return values; } } pub…

Your sort solution limits which algorithms can be used, because you can't pass in a Func which might need an additional parameter anymore. This is why most C# developers would use an interface for this. With an interface you add extra parameters or dependencies to the constructor of the concrete implementation. If this example wasn't sort algorithms but password hashing algorithms this would be clear. So yeah.. it pr…

  void List Sort(List input, bool someParam){}

  var values = new List { 9, 1, 5, 7 };
  DoSomething(x => Sort(x, true), values);
  

Post by AdeptusAquinas » Tue, Dec 18, 2018, 9:32 PM UTC

algorithmsRcool wrote: post #69

dustinmoris wrote: post #68

Earlier quoted context omitted.

Your sort solution limits which algorithms can be used, because you can't pass in a Func which might need an additional parameter anymore. This is why most C# developers would use an interface for this. With an interface you add extra parameters or dependencies to the constructor of the concrete implementation. If this example wasn't sort algorithms but password hashing algorithms this would be clear. So yeah.. it pr…

Just to be clear, you are arguing the superiority of partial application/currying here right? Because your F# example is the same except it's trading Func , List for (int list -> int list)

Post by quickthrower2 » Tue, Dec 18, 2018, 9:33 PM UTC

steelframe wrote: post #48

Someone I interviewed some years back did their interview in F#. I didn't know F# and tried to make that abundantly clear to them, but they persisted nonetheless. I had messed around with O'Caml back in college and so at least had a passing familiarity with functional language concepts, but I really had no idea if what the candidate produced could be considered quality production code. That didn't help their chances…