Comment by Marcus Pohorely on "Is using Redux an overkill for simple front-ends?"

CommentIs using Redux an overkill for simple front-ends?

Marcus Pohorely

CTO/CEO @Pagelanes.com

Aug 18, 2016

No. Sure it's good for big apps to keep their store updated all the time, but also for small apps it's good. The implementation is easy for your usecase. One Endpoint in the store, one reducer and maybe 3 actions, and off you go. The ease of the implementation makes Redux also useable for small things. Because Why not? keeping everything clean is a nice goodie ;)

So basically: It's definitly no overkill, but for sure you could to small things without redux too. But then you can ask the following question too: Do i really need React for this App or could i simply use one Vue.js View too? (Which might be easier in this case).

Marcin Piekarski

Aug 19, 2016

Just wanted to quickly add that if he did go down the Vue.js path.

He could implement a simple way of keep state to start off with and then if the complexity increases, switch to using Vuex, which is somewhat similar to Redux.

React/Redux or Vue/Vuex. Both are fun to use.

"Because why not?" => To keep the application as simple as possible. Use abstractions carefully and only if needed. Otherwise you are just making your application more complex for no reason. Also be aware of other disadvantages of using Redux.

You could say the same "Because why not?" to

1) Any dependency injection framework

2) Extracting explicit interfaces for each class

3) Usage of a logging framework instead of simple console.log

4) Pick any another abstraction or indirection framework.

Search Hashnode