> because it's going to run every time you get a newState. Didn't have to in the past. Back with class-based components we had shouldComponentUpdate(), and lo

> because it's going to run every time you get a newState. Didn't have to in the past. Back with class-based components we had shouldComponentUpdate(), and lost that when components switched to pure functions.