35 engineers on Hacker News describe using F# first-hand: 18 endorse it, 3 regret it, 4 are mixed.
“I have several f# services (suave, giraffe) in prod and agree that things have been only trending positive.”
mixed · production · banashark · 2024-12-15 · source ↗ · wrong label?“I'm recently enjoying F# a lot. What really sold it was partial application and absolutely bonkers type inference”
endorse · personal · neonsunset · 2024-11-27 · source ↗ · wrong label?“we completely rewrote the application in Typescript and Rust.”
regret · production · 1 yr · obeavs · 2024-11-10 · source ↗ · wrong label?“Right now in my context personally I could use F# for my company's apps and not hit too many blockers”
endorse · production · akra · 2022-12-17 · source ↗ · wrong label?“I used F# a bit and learned a lot from it, and the same with Elixir and Nerves.”
endorse · personal · elcritch · 2022-11-23 · source ↗ · wrong label?“The safety and clarity it provides by allowing you to use F# type system is a vast improvement over JS.”
endorse · production · jordanmarr · 2021-12-21 · source ↗ · wrong label?“I've been using F#, Giraffe, Fable.React/Feliz, and Fable.Remoting in production for the past four years.”
endorse · production · 4 yr · aaronmu · 2021-12-20 · source ↗ · wrong label?“for the .net ecosystem we use C# of F# depending on how relaxed the engineering team and the stakeholders”
endorse · production · StreamBright · 2021-12-11 · source ↗ · wrong label?“We've been running F# in production since 2014 - almost 7 years.”
endorse · production · 7 yr · nbevans · 2020-12-05 · source ↗ · wrong label?“We're using F# in prod (about 200K LOC) and it has been great so far.”
endorse · production · JaggerJo · 2020-11-03 · source ↗ · wrong label?“F# is the language I want to like... but it constantly feels like the ignored step-child. The REPL is great in theory, but trying to import packages is a nightmare every time I try.”
regret · personal · FridgeSeal · 2020-06-09 · source ↗ · wrong label?“I ported a 10kloc F# codebase to a very alien-looking functional-style C#. The project was processing several hundred thousand dollars woth of transactions per month”
endorse · production · davidgrenier · 2018-12-28 · source ↗ · wrong label?“It works great especially with f# and giraffe.”
endorse · personal · slaveoftime · 2018-12-19 · source ↗ · wrong label?“I've been diving into f# in 2018... it really made me a better developer. My experience hasn't been great [with tooling]. It works, but it has been pretty unreliable.”
mixed · personal · winkelwagen · 2018-12-18 · source ↗ · wrong label?“using F# in production for 5 years now, I have gone back to classes and interfaces in almost all cases.”
mixed · production · 5 yr · daxfohl · 2018-12-18 · source ↗ · wrong label?“the lack of type classes & HKTs meant we kept having to repeat ourselves... I would love to use F# again, but not until the language adds those features.”
mixed · production · runT1ME · 2017-08-16 · source ↗ · wrong label?“I'm running it in prod since last year and from the runtime perspective there are no issues.”
endorse · production · 1 yr · insulanian · 2016-06-10 · source ↗ · wrong label?“I like F# a lot, by the way. I can't wait to use it more.”
endorse · personal · KirinDave · 2015-11-20 · source ↗ · wrong label?“I'm having great fun writing F# code in Linux with Vim”
endorse · personal · mmavnn · 2014-12-31 · source ↗ · wrong label?“Coming from a strong OOP background... once I came to grips with the power of the language, I didn't look back.”
endorse · production · DanielBMarkham · 2014-12-31 · source ↗ · wrong label?“The prototype version was written in F#, but that means you're anyways fighting memory allocation, which was the single biggest performance issue in my program.”
regret · personal · MichaelGG · 2014-12-12 · source ↗ · wrong label?“I can't say enough good things about F# and about Mono.”
endorse · production · MichaelGG · 2014-11-13 · source ↗ · wrong label?“Tachyus uses F# almost exclusively. We have had great success with it. Just released 2.0 of our stack to production.”
endorse · production · jackfoxy · 2014-11-13 · source ↗ · wrong label?“We use F# for a fairly large production service, and we'll hang around here answering questions if you have any.”
endorse · production · architgupta · 2014-11-12 · source ↗ · wrong label?“The main benefit I've had from having access to the source is being able to figure out exactly how things work.”
endorse · personal · MichaelGG · 2010-11-05 · source ↗ · wrong label?“I'm also a daily user of F#, and like you I'm not totally sold on this alternative.”
neutral · production · nozzlegear · 2024-12-22 · source ↗ · wrong label?“I have no problem refactoring large Scala apps or F# apps or even Rust apps”
neutral · production · darksaints · 2022-11-03 · source ↗ · wrong label?“Global type-checking between C# and F# projects comes out-of-the-box (but you have to design the shared types properly)”
neutral · production · victorNicollet · 2022-03-15 · source ↗ · wrong label?“We use this technique to auto-generate admin panels.”
neutral · production · tejasv · 2020-12-05 · source ↗ · wrong label?“I used EventStore in production for 2 years with F#.”
neutral · production · 2 yr · slowmovintarget · 2018-11-04 · source ↗ · wrong label?“I even had the opportunity to try the F# Type Provider for Sencha Architect”
neutral · personal · davidgrenier · 2014-10-24 · source ↗ · wrong label?“I have an outstanding code editor and development environments for Lisp, Scheme, Python, J, F# and JavaScript.”
neutral · personal · taylodl · 2012-11-25 · source ↗ · wrong label?“I've been using F# (the only functional programming language I've ever tried out) for just a few days”
neutral · personal · lifebeyondfife · 2011-11-25 · source ↗ · wrong label?“I have been programming Python for many years now, along with a mix of C#, Scala and some F#.”
neutral · personal · jeswin · 2010-08-08 · source ↗ · wrong label?