←back to thread

Why F#?

(batsov.com)
438 points bozhidar | 1 comments | 01 Apr 25 12:34 UTC | HN request time: 0.327s | source
Show context
eknkc ◴[01 Apr 25 12:45 UTC] No.43546122[source]▶
As far as I can tell F# is one of those things where every single user is extremely happy. This happens rarely and I really am curious about the thing but never had time to get into it. I'm also pretty well versed in the .net ecosystem so it's probably gonna be easy.

Any tips? What kind of workflows might benefit the most if I were to incorporate it (to learn..)?

replies(4): >>43546205 #>>43546241 #>>43546333 #>>43548384 #
1. munchler ◴[01 Apr 25 12:56 UTC] No.43546241[source]▶
F# shines on the back end, where its functional-first style is very adept at crunching data. Think about data flows in your system: Any place where you use LINQ in C# today to select/filter/transform data might be even better in F#. Parsing is also a great F# use case (e.g. parser combinators), although a fairly narrow niche.