Dan Shappir
Mar 19, 2017 · 1 min read

The biggest problem with setState is simply that it has a wrong, misleading name. It should have been called something like asyncShallowMergeState (yes, I know it’s a mouthful ;-) Oh, and it should have returned a Promise.

    Dan Shappir

    Written by

    I’m a Performance Specialist at Wix.com. My job is to make 80 million websites hosted on the Wix platform load and execute faster. Opinions are my own