Why calling setState method doesn't mutate the state immediately?

Question

Ok, i\'ll try and make this quick because it SHOULD be an easy fix...

I\'ve read a bunch of similar questions, and the answer seems to be quite obvious. Nothing I wo

Answer 1

This is by-design due to performance considerations. setState in React is a function guaranteed to re-render Component, which is a costly CPU process. As such, its designers wanted to optimize by gathering multiple rendering actions into one, hence setState is asynchronous.