Hacker News new | ask | show | jobs
by ng12 3610 days ago
You don't need all of that from scratch. You can just build React components, and when it comes time to add a store or a router the only thing you need to change are the glue components that bind things together. I think it works out nicely -- the dev process is as composable as the app itself.
2 comments

Yea I've noticed that. The react community likes to focus on examples involving a sign up form with 3 fields where you "really don't need all of that". Except that is not what most of us SPA devs are building. We need most of that.
Either you need all of that, and the time to set it up is absolutely insignificant compared to the lifetime of the project.

Or you don't need all of that.

It's very, very rarely a different situation.

Is that really an argument? that you don't need to write it at the beginning? you still have to do it...
My argument is that it's a net benefit. Composable architectures are not boilerplate. Remember that there was a time when almost all React apps where written with Flux -- this model is what allowed Redux gain traction.