title: Why use redux-persist over manually persisting state to localStorage?
body: <p>Another way to ask would be, if you really only want to start your app up with the data saved in localStorage (rehydrate) and save every redux state change to localStorage (persist) is using <a href="https://github.com/rt2zz/redux-persist" rel="noreferrer">redux-persist</a> any better than using your own solution like <a href="https://egghead.io/lessons/javascript-redux-persisting-the-state-to-the-local-storage" rel="noreferrer">Dan Abramov explains here</a>?</p>
  <p>I understand redux-persist comes with a lot of other features, and I myself started using it to be able to use redux-persist-crosstab (to be able to deal with changes between apps running in different tabs), but I wonder if it's overkill to use it for the most basic scenario. Especially since it's harder to understand and sometimes does funny stuff, like calling <code>persist/REHYDRATE</code> randomly.</p>
  <p>Am I missing anything obvious here?</p>