What is the case against F#? (2009)
stackoverflow.com
What is the case against F#? (2009)
1–10 of 107 posts
Re: What is the case against F#? (2009)
#2"Asked 11 years, 7 months ago"
Has the need to use functional programming languages become obvious yet? Has C/C++ et al. fallen by the wayside, yet?
Re: What is the case against F#? (2009)
#3I have frequently come across 'multi-core' code using fancy features of fancy languages (e.g. Scala) that get a 205% speedup on a 8 core machine when I should be getting more of a 750% speedup, not get the same answers every time, etc.
The choice in that situation is to risk spending a few days debugging (50% at best success rate) or spend 20 minutes and use a ThreadPoolExecutor and you're done.
Java was the first programming language specced out by adults, and early to get a correct memory model and correct concurency primitives. 'correct' is a much better attribute than 'new' or 'shiny'.
Re: What is the case against F#? (2009)
#4"Asked 11 years, 7 months ago" Has the need to use functional programming languages become obvious yet? Has C/C++ et al. fallen by the wayside, yet?
Didn't they add lambdas to C?
Re: What is the case against F#? (2009)
#5"Asked 11 years, 7 months ago" Has the need to use functional programming languages become obvious yet? Has C/C++ et al. fallen by the wayside, yet?
C/C++ have not fallen to the wayside but most major programming languages have now inherited quite a few functional paradigms. I haven't kept up to date, but don't both C++ and Java have lambdas now? Don't they also feature currying? C++ is of course not Haskell, but that's not the point. Functional programming has become commonplace by procedural languages adopting the simpler/most-useful aspects.
Re: What is the case against F#? (2009)
#6“Most 'developers' don't understand functional programming concepts, and can't even write very good imperative code in C#. So what hope have they got of writing good functional code in F#?”
i hope 11 years later we have a different attitude
Re: What is the case against F#? (2009)
#7Why You Should Use F# (2018)(HN): https://news.ycombinator.com/item?id=26142696
Introduction to the 'Why use F#' series (2012) (HN): https://news.ycombinator.com/item?id=26142662
... in case anyone thinks I am against using F#. Important to know the pros-and-cons.
Re: What is the case against F#? (2009)
#8“Most 'developers' don't understand functional programming concepts, and can't even write very good imperative code in C#. So what hope have they got of writing good functional code in F#?” i hope 11 years later we have a different attitude
What's wrong with that attitude and what do you think should be better by now?
Re: What is the case against F#? (2009)
#9I have frequently come across 'multi-core' code using fancy features of fancy languages (e.g. Scala) that get a 205% speedup on a 8 core machine when I should be getting more of a 750% speedup, not get the same answers every time, etc. The choice in that situation is to risk spending a few days debugging (50% at best success rate) or spend 20 minutes and use a ThreadPoolExecutor and you're done. Java was the first pr…
The other thing is that most programs are probably doing nothing most of the time. Waiting for user input, waiting for network IO, waiting for some other real-world event.
For most developers, it's probably not using another language so you can "wait faster" most of the time. The performance sensitive code can be scrutinised and properly optimised on a case-by-case basis.
Re: What is the case against F#? (2009)
#10Most of the time my C# code uses most of the functional paradigms. I write pure functions when i can and use LINQ almost everywhere. Recently i created a F# API with the dotnet CLI, but the syntax is not even close. I get the concepts, but syntax is a little bit to much to just try it when i have to write a new microservice. Am i the only one?