2019-01-19
1570
#react#redux
Christian Nwamba
1815
Jan 19, 2019 ⋅ 5 min read

When (and when not) to use Redux

Christian Nwamba JS preacher. Developer 🥑. Building the web with the community @concatenateConf @forLoopAfrica. JS and Senior Advocacy for the Next Billion Users through Microsoft.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

7 Replies to "When (and when not) to use Redux"

  1. Why would anyone EVER use redux? Because they aren’t aware of MUCH simpler ways to solve the same problems.

  2. What exactly did you show in the example please?

    – how redux dispatch is called -> OK, shown
    – how programming a reducer is used to modify a shared state (redux store) -> OK, shown

    But the most important thing is — where is the actual logic?
    Where is the functional programming you are talking about?

    I don’t see any functionality, just a way to store information into a shared state.

Leave a Reply