Products · Product
F#
Raised as a usability problem by 67 people on Hacker News over 18 years (2009–2026), in 63 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Learning materials assume C# knowledge beginners lackUnreviewed
20092026- Tutorials assume prior experience elsewhere and library docs lead to frustrating awkward setups2022-06-26
- Learning materials assume C# knowledge that a beginner lacks, so they are hard to follow2020-05-20
- Documentation and books assume a C# background, leaving newcomers without a way to learn2019-08-04
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Mixing tabs and spaces for alignment forces users to inspect whitespace closely2026-06-24
- C# programmers find F# library types downright impossible to figure out2025-11-07
- No reliable hot reload, so the AI leaves servers running and then hits startup errors2025-08-09
- IDE support is minimal and documentation and examples are hard to find2025-04-09
- Command-line tooling on Linux is frustrating to use and inherits C# baggage2025-04-01
- Visual Studio's F# support was poor, so the commenter found it hard to work with2024-11-10
- Tooling and tutorials for MAUI assume C#, making F# awkward2024-10-07
- Must manually reorder files in the IDE; hard to find them2024-09-14
- Unclear when to use classes versus modules or functions versus members2024-06-17
- Piping gives type inference errors where the equivalent function call compiles, forcing two conventions2024-03-30
- Explicit delaying and forcing of values clutters code wherever laziness is used2023-03-27
- Tooling was so hard to set up that non-trivial examples would not run2023-02-11
- F# REPL on Linux is a mess and mostly unusable2022-11-02
- Documentation was immature, inconsistent, or broken for F#2022-08-16
- F# tooling breaks autocomplete and features fail to work as advertised, wasting debugging time2022-07-25
- Tutorials assume prior experience elsewhere and library docs lead to frustrating awkward setups2022-06-26
- Had to disable F# projects just to get intellisense working2022-06-17
- Confusing type provider errors the commenter never managed to resolve2022-06-17
- Curried int -> int -> int signatures make it hard to spot call errors2021-12-16
- Unclear which data type definition to use, and what each implies2021-12-16
- Special characters in the name make it hard to search for and find2021-10-15
- Tried twice to use F# on Mac, gave up because tooling and docs didn't work2021-06-25
- With many type providers the editor breaks and compilation becomes very slow2021-04-26
- Events need heavy ceremony and missing implicit conversions make some C# libraries unusable2021-04-09
- F# syntax is hard to pick up when starting a new service2021-02-15
- Diagnosing type errors requires understanding Hindley-Milner type inference, which gets worse with more features2021-02-01
- Function signatures are opaque at a glance and hard to reason about2021-02-01
- Heavily functional code with partially applied functions is very hard to read2021-02-01
- F# tooling is broken and IDE support is weaker than for C#2021-01-13
- Updating records inside a list is so convoluted it requires lenses, making a trivial task hard2020-10-10
- Third-party libraries are poorly documented, making them hard to understand and use2020-10-05
- Can't tell from past code what types are, since they are invisible and hidden behind abstractions2020-09-27
- Importing packages in the REPL is a nightmare every time2020-06-09
- Pipelines are hard to debug, needing a dedicated pipeline debugger2020-05-21
- Lack of tooling makes everyday development harder, with more friction than C#2020-05-20
- Learning materials assume C# knowledge that a beginner lacks, so they are hard to follow2020-05-20
- Following the tutorial with the CLI produced only errors, so the person gave up2020-05-08
- F# tooling has been bad for ages and disrupts normal workflow2019-09-23
- Documentation and books assume a C# background, leaving newcomers without a way to learn2019-08-04
- Can't find the API for the Result module; it's missing from the core namespace docs2019-07-04
- Hours of failure compiling hello world due to missing setup instructions2019-05-22
- Explanations not expedient and show too many ways of doing things2019-03-03
- Spends lots of time searching for idiomatic approaches that don't exist; documentation is poor2019-02-22
- Official guides fail on Mac, forcing users to search error messages themselves2019-02-22
- Async syntax is confusing to a C# developer2019-01-26
- Main thread pauses a second or two on every code edit, making it painful to use2018-12-28
- Confusing choice between .NET versions and hard setup, leading to abandonment2018-12-19
- Hard to find implementations and unwieldy with many dependencies2018-12-18
- Software feels slow and bloated, making the user wait2018-12-18
- Typing a record instance gives compiler warnings and makes field order hard to see2018-12-18