title: What is wrong with setState?
body: <p>Flutter <code>setState</code> is a built-in state management approach listed in the Flutter official documentation along with a list of other libraries for state management
  <a href="https://docs.flutter.dev/development/data-and-backend/state-mgmt/options" rel="nofollow noreferrer">https://docs.flutter.dev/development/data-and-backend/state-mgmt/options</a></p>
  <p>Why are there so many state management alternatives to Flutter native <code>setState</code>  such <code>RiverPod</code>, <code>GetX</code>, <code>BloC</code>, <code>Redux</code>...? What is so bad with <code>setState</code> that motivates so many state management libraries to come into existence.</p>
  <p>This is to the point that Flutter itself is endorsing those libraries by putting them on their official documentation.</p>
  <p>Does it all come down to just performance? If so, do we have actual performance data that has proven that <code>setState</code> is very bad?</p>