RxJS

Raised as a usability problem by 12 people on Hacker News over 6 years (2019–2024), in 8 threads.

People raised many different problems with RxJS, 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

Complex RxJS pipelines are hard to understand and maintain months later2024-10-04
Simply comparing one value requires awkward pipes and RxJS complexity2024-03-21
Call stacks and debugger become useless, forcing console.log debugging everywhere2023-05-04
Operator names became opaque and the API less approachable to learn2023-05-04
Hard to read at a glance; needs training to understand what code is doing2023-05-03
Commenter can never remember how to use RxJS, finds it unintuitive2023-05-03
Hard to read and hard to build a mental model of what happens2023-05-03
Simple things become mindbogglingly complex; developers can't tell what code does2022-08-16
Event flow is hard to follow and bugs are hard to debug2020-11-12
Unclear how streams connect and which columns are interactive inputs2019-09-13
API is clunky and poorly designed, causing long ramp-up time for learners2019-08-30
Easy to misuse; subscriptions cause hidden side effects and forgotten unsubscribes2019-03-28