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:

SOLID series: The Open-Closed Principle

Today, we’ll be exploring the Open-Closed Principle: from the criticisms around it, its best use cases, and common misapplication.

Oyinkansola Awosan
May 16, 2025 ⋅ 11 min read
Simplifying E2E Testing With Open Source AI Testing Tools

AI-powered e2e testing: Getting started with Shortest

Explore how AI-driven testing tools like Shortest, Testim, Mabl, and Functionize are changing how we do end-to-end testing.

Jude Miracle
May 16, 2025 ⋅ 11 min read
profit center vs. cost center: How company structure affects engineering

Profit center vs. cost center: How company structure affects engineering

Examine the difference between profit vs. cost center organizations, and the pros and cons these bring for the engineering team.

Marie Starck
May 15, 2025 ⋅ 4 min read
How to pass a TypeScript function as a parameter

How to pass a TypeScript function as a parameter

Explore how to pass functions and structured objects as parameters in TypeScript, including use cases, syntax, and practical scenarios.

Kealan Parr
May 15, 2025 ⋅ 10 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