ReasonML

Raised as a usability problem by 11 people on Hacker News over 7 years (2018–2024), in 9 threads.

People raised many different problems with ReasonML, but no single problem has yet been raised by 3 people in 3 different months and threads.

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 12 complaints

Compiler error messages are very confusing to the programmer2024-03-06
Confusing inconsistencies across OCaml, Bucklescript and Reason/ReScript toolchain2021-01-16
Function argument order differs between Belt and the standard library2020-06-09
Multiple overlapping standard libraries are very confusing for beginners2019-09-16
Many bs annotations needed for interop, cryptic compiler errors, and runtime errors remain2019-09-04
Lacks async/await syntax, forcing cumbersome callback chaining2019-09-04
Off the beaten path, unclear which docs to read and errors are confusing2019-03-03
Steep learning curve due to lack of beginner-friendly documentation2018-11-20
Steep learning curve due to lack of beginner-friendly documentation2018-11-10
Interoperating between Reason, BuckleScript, OCaml and build tools is confusing and ill-defined2018-11-10
JS interop syntax is very unintuitive and hard to understand2018-11-10
Installation problems, compiler bugs, and esoteric compiler errors made it hard to get work done2018-09-07