←back to thread

Why F#?

(batsov.com)
438 points bozhidar | 1 comments | | HN request time: 0.201s | source
Show context
eknkc ◴[] 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 #
JohnyTex ◴[] No.43548384[source]
Personally I think F# is excellent for writing ye olde CRUD applications, especially as the business logic becomes more complex. F# is really good at domain modeling, as creating types comes with minimal overhead. C# has improved a lot in this area (eg record types) but it’s still got a long way to go.

I wrote a tutorial about how to get up and running with web dev in F# that might be of interest: https://functionalsoftware.se/posts/building-a-rest-api-in-g...

replies(1): >>43555850 #
1. DeathArrow ◴[] No.43555850[source]
Thank you, for someone interested in using F#, that is great.

I see you use Giraffe but I wonder how hard would it be to use Web API or to mix F# projects with C# projects in the same solution.