How do you explain the term Predictable State Container in simple words?

View other answers to this thread
Start a personal dev blog on your domain for free and grow your readership.

3.4K+ developers have started their personal blogs on Hashnode in the last one month.

Write in Markdown · Publish articles on custom domain · Gain readership on day zero · Automatic GitHub backup and more

Dan Abramov's photo

It's a "state container" because it holds all the state of your application. It doesn't let you change that state directly, but instead forces you to describe changes as plain objects called "actions". Actions can be recorded and replayed later, so this makes state management predictable. With the same actions in the same order, you're going to end up in the same state.

Pawel Majewski's photo

Sorry Dan Abramov, your answer is describing what is and how works Redux. It sounds for me like "Redux is Redux State Container". But what means that the state container is Predictable ? How to describe Predictable term without any reference to Redux (implementation details) ? I guess there are other state containers which can be described as Predictable (and do not have nothing common with Redux, actions, ect..) :)

Fernando Souza's photo

My answer can be silly, but Redux concepts help to explain and understanding the meaning of predictable in this context. That means that you always know from where the state comes from, (from the store), who will be able to update it, (Actions).