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.
Ask QuestionStart a discussion, ask a question, or ask for an opinion on a particular technology
Write StoryWrite an article on something you learned today or your experience with a technology
Start PollConfused with something? Ask the community for their opinion
Submit NewsFound an interesting article on the web? Share it with the community.