Redux FAQ: General
Table of Contents
- When should I learn Redux?
- When should I use Redux?
- Can Redux only be used with React?
- Do I need to have a particular build tool to use Redux?
When should I learn Redux?
- Deciding What Not To Learn
- How to learn web frameworks
- Redux vs MobX vs Flux vs... Do you even need that?
- Ask HN: Overwhelmed with learning front-end, how do I proceed?
- Twitter: If you want to teach someone to use an abstraction...
- Twitter: it was never intended to be learned before...
- Twitter: Learning Redux before React?
- Twitter: The first time I used React, people told me I needed Redux...
- Twitter: This was my experience with Redux...
- Dev.to: When is it time to use Redux?
When should I use Redux?
The need to use Redux should not be taken for granted.
As Pete Hunt, one of the early contributors to React, says:
You'll know when you need Flux. If you aren't sure if you need it, you don't need it.
Similarly, Dan Abramov, one of the creators of Redux, says:
I would like to amend this: don't use Redux until you have problems with vanilla React.
In general, use Redux when you have reasonable amounts of data changing over time, you need a single source of truth, and you find that approaches like keeping everything in a top-level React component's state are no longer sufficient.
However, it's also important to understand that using Redux comes with tradeoffs. It's not designed to be the shortest or fastest way to write code. It's intended to help answer the question "When did a certain slice of state change, and where did the data come from?", with predictable behavior. It does so by asking you to follow specific constraints in your application: store your application's state as plain data, describe changes as plain objects, and handle those changes with pure functions that apply updates immutably. This is often the source of complaints about "boilerplate". These constraints require effort on the part of a developer, but also open up a number of additional possibilities (such as store persistence and synchronization).
In the end, Redux is just a tool. It's a great tool, and there are some great reasons to use it, but there are also reasons you might not want to use it. Make informed decisions about your tools, and understand the tradeoffs involved in each decision.
- When (and when not) to reach for Redux
- The Tao of Redux, Part 1 - Implementation and Intent
- You Might Not Need Redux
- The Case for Flux
- Twitter: Don't use Redux until...
- Twitter: Redux is designed to be predictable, not concise
- Twitter: Redux is useful to eliminate deep prop passing
- Twitter: Don't use Redux unless you're unhappy with local component state
- Twitter: You don't need Redux if your data never changes
- Twitter: If your reducer looks boring, don't use redux
- Reddit: You don't need Redux if your app just fetches something on a single page
- Stack Overflow: Why use Redux over Facebook Flux?
- Stack Overflow: Why should I use Redux in this example?
- Stack Overflow: What could be the downsides of using Redux instead of Flux?
- Stack Overflow: When should I add Redux to a React app?
- Stack Overflow: Redux vs plain React?
- Twitter: Redux is a platform for developers to build customized state management with reusable things
Can Redux only be used with React?
Redux can be used as a data store for any UI layer. The most common usage is with React and React Native, but there are bindings available for Angular, Angular 2, Vue, Mithril, and more. Redux simply provides a subscription mechanism which can be used by any other code. That said, it is most useful when combined with a declarative view implementation that can infer the UI updates from the state changes, such as React or one of the similar libraries available.
Do I need to have a particular build tool to use Redux?
<script> tag. As the relevant pull request says:
The new Counter Vanilla example is aimed to dispel the myth that Redux requires Webpack, React, hot reloading, sagas, action creators, constants, Babel, npm, CSS modules, decorators, fluent Latin, an Egghead subscription, a PhD, or an Exceeds Expectations O.W.L. level.
Nope, it's just HTML, some artisanal
<script>tags, and plain old DOM manipulation. Enjoy!