A Case for setState
Zack Argyle

Software engineering practices are a pendulum… The pendulum swings one way, people get burnt, then it swings the other way, people get burnt and make it swing back, forgetting about what happened last time. And back and forth and back and forth.

In one end of the Pendulum, you have the Backbone and Angular state management, and early days React, and that was bad. Flux came in, and it was okay-ish. Redux came and it was pretty good. People abused it, overcomplicated things, and complaining about the boilerplate, and making the pendulum swing back. But unless your app is trivial, the same thing will happen as last time the pendulum went that way :)

Like what you read? Give Francois Ward a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.