←back to thread

Why F#?

(batsov.com)
438 points bozhidar | 1 comments | 01 Apr 25 12:34 UTC | HN request time: 0.213s | source
Show context
pimbrouwers ◴[01 Apr 25 13:24 UTC] No.43546526[source]▶
Our shop converted 6 years ago, from C# to exclusively F#. I also author and maintain some packages (falco, donald, validus and others). The language is tough to learn if you're coming from a C-style language. But worth the effort and experience. It's extremely concise a true delight to build programs in that are fast, robust and durable.

There are a few drawbacks, depending on your perspective:

- compilation is slower than c# and hot reload isn't supported (it's in progress)

- there are very few opportunities to use it professionally

- hiring devs can be challenging

replies(5): >>43546728 #>>43546760 #>>43548900 #>>43552429 #>>43554801 #
z5h ◴[01 Apr 25 13:49 UTC] No.43546760[source]▶
As a proficient Elm developer with industry experience, I’m wondering what are the biggest challenges in hiring devs? Is it the paradigm, learning the ecosystem, lack of interest? Are you currently hiring?
replies(2): >>43546872 #>>43555250 #
1. Akronymus ◴[01 Apr 25 13:58 UTC] No.43546872[source]▶
As someone who quite likes f#: It seems like a chicken and egg problem, not many companies doing f# because not many devs know it and not many devs learning it because not many companies are doing it.

I certainly wish I were doing f# professionally, but I only ever found 1 job listing for it, and that was in vienna while I am located like 200km away from it :(

Speaking of elm: I really like elmish for the frontend, when I need to make a dynamic page in the first place. Maybe that could be to your interest? (It transpiles to react under the hood via fable, which you can webpack into a drop in bundle. But I digress)