Products · Product
Redux
Raised as a usability problem by 46 people on Hacker News over 12 years (2015–2026), in 45 threads.
No issue was raised by at least 3 people in 3 threads this year.
Every issue, all time, most people first
Redux has boilerplate and confusing terminologyUnreviewed
20152026- Redux setup is extremely confusing to a backend engineer2026-08-14
- Redux API is very unintuitive and hard to understand2026-02-16
- Redux requires too much boilerplate code for simple state management2022-03-29
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
- Redux setup is extremely confusing to a backend engineer2026-08-14
- Redux API is very unintuitive and hard to understand2026-02-16
- Adding one button with an action requires changing four files in seven places2024-02-27
- Hard to trace through in an IDE; boilerplate spread across files, confusing behind-the-scenes behavior2022-12-26
- Every store change requires editing about five files, slowing feature work and making code hard to trace2022-07-28
- Can't find all consumers of a reducer's state, must grep through every useSelector or connect call2022-07-03
- Redux requires too much boilerplate code for simple state management2022-03-29
- Redux is confusing and stringy, hard to understand the fundamentals of2022-03-09
- Typing into sites built with Redux lags badly, about a second per character2022-03-03
- Newcomers can't tell what a slice is from the naming alone2021-03-25
- Async logic in createSlice requires a separate createAsyncThunk, which is confusing and fragmented2021-03-25
- Table must be refreshed after an edit despite already receiving new values from the server2021-02-11
- Too much information to learn; setup section highlights around 50 things to remember2020-11-15
- Redux's terminology like reducers is hard to explain and grasp2020-10-29
- Writing reducers is verbose and unintuitive, with pitfalls needing many addons2020-08-19
- Docs assume prior Redux knowledge, so newcomers can't easily start with the toolkit2020-06-18
- Redux requires too much boilerplate code to accomplish simple state updates2020-05-29
- Small features require touching five files and redundant constant boilerplate2020-01-02
- Learning Redux involves too much delay and no fast feedback loop; overwhelms newcomers with choices2020-01-01
- Overwhelming for beginners, with lots of boilerplate to set up2020-01-01
- Hard to trace implementations because logic is spread across many files2019-02-09
- Hard to debug when something doesn't work; too many moving parts2018-12-30
- Requires accepting several principles and many middlewares, feeling heavy and burdensome to adopt2018-12-05
- Writing large amounts of repetitive boilerplate for actions, types and exports2018-10-15
- Searching for a specific topic yields nothing because it's skipped as not commonly used2018-06-27
- Poor, unintuitive naming makes Redux hard to learn, especially for experienced programmers2018-06-20
- Writing complex shouldComponentUpdate logic causes many mistakes and poor performance2018-06-19
- Redux is non-intuitive, with lots of boilerplate and confusing terminology2018-05-09
- Documentation uses complicated concepts and is hard to understand2018-04-25
- Redux is considered horrible to use, with no specific problem stated2018-03-26
- Too much boilerplate to change state through actions and reducers2018-03-05
- Redux names are confusing, so users must mentally translate them into event-system terms2018-01-11
- Structure is confusing up front and makes no sense to newcomers2017-11-20
- Redux requires an excessive amount of boilerplate and laborious action construction2017-09-27
- Redux-Persist docs reference PersistGate, which the author can't find; fragmented, confusing setup2017-08-19
- Developers must write verbose immutable update code and manage re-renders manually2017-07-06
- Hard to tell what a button or event does because logic is split across many files2017-06-30
- Pages of documentation say little, misleading newcomers about what they're learning2017-06-14
- Confusing 'action' terminology and tutorial code make Redux hard to understand2017-05-06
- Toggling one view element requires editing five files, with heavy boilerplate2017-05-05
- Confusing names like reducer and mapStateToProps mislead beginners about what they do2017-05-05
- Requires too much plumbing code for simple state management, making it tedious to use2017-05-05
- Hard to tell which parts of Redux are core versus added convention2017-04-24
- Developer must keep re-checking docs because the core concepts are hard to remember2017-04-22
- Redux is too convoluted with abstract concepts; 'reducer' name only makes sense after understanding2016-12-11
- Too much boilerplate and idiosyncratic names to learn and use2016-10-21
- Awesome-redux list is cluttered and poorly organized, hard to navigate2016-10-18
- Showing one element on click requires writing too much boilerplate, slowing development2016-09-15
- Full immutability and funneling everything through functions obscures code readability2016-08-14
- Simple menu toggle requires writing many boilerplate pieces, and stale state makes modals appear randomly2016-07-11