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:

How to eliminate render-blocking resources — CSS and JavaScript

How to eliminate render-blocking resources — CSS and JavaScript

Use Lighthouse to eliminate render-blocking resources, which block the first paint of your page, in both CSS and JavaScript.

Anna Monus
Apr 4, 2025 ⋅ 8 min read
Mocking Complex APIs With Mirage JS

Mocking complex APIs with Mirage JS

Mock complex APIs with JavaScript’s Mirage JS library including JWT authentication, relational data, role-based access control, and more.

Emmanuel John
Apr 4, 2025 ⋅ 10 min read
8 best Go web frameworks for 2025

The 8 best Go web frameworks for 2025: Updated list

Looking for the best Go frameworks? Compare the top 8 Go web frameworks for 2025, including Gin, Fiber, Echo, and Beego, with pros, cons, and performance insights.

Victor Jonah
Apr 3, 2025 ⋅ 15 min read
Making Your First Game In Excalibur.js

Game development for frontend: Building with Excalibur.js

Build your first 2D browser game using JavaScript and the Excalibur.js library, covering essential game development concepts.

Yashodhan Joshi
Apr 3, 2025 ⋅ 25 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