Step by Step Guide to Building React Redux Apps

If you want a guide to doing this with a &quot;here are some specific libraries we will use today&quot; perspective and automated testing, take a look at <a href="http:&#x2F;&#x2F;teropa.info&#x2F;blog&#x2F;2015&#x2F;09&#x2F;10&#x2F;full-stack-redux-tutorial.html" rel="nofollow">http:&#x2F;&#x2F;teropa.info&#x2F;blog&#x2F;2015&#x2F;09&#x2F;10&#x2F;full-stack-redux-tutorial...</a>

It&#x27;s really disappointing to me to see Redux being the &quot;defacto standard&quot; for React applications. It&#x27;s overly decoupled for simple applications, which makes it harder to reason about the application. It also doesn&#x27;t help that the Redux codebase itself is hard to understand.<p>It is only a tool you should reach for after you find you need it. Too few developers approach software development with this level of pragmatism and instead we get &quot;use X because it&#x27;s being used&quot;. I guess you need to understand the tool to know when to use it - but that doesn&#x27;t mean it should become the &quot;defacto standard&quot;.<p>Ironically Redux is being coupled with React, which is a great library for structuring UI into components and resulting it simpler to understand code.

Wow what an absolute nightmare to wrap my head around. Reminds me of J2EE days of abstract patterns everywhere just because we can. Talk about simplicity.<p>Here is the same app in 130 lines:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;techlayer&#x2F;espresso.js&#x2F;blob&#x2F;master&#x2F;examples&#x2F;todomvc&#x2F;app.js" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;techlayer&#x2F;espresso.js&#x2F;blob&#x2F;master&#x2F;example...</a>

The &quot;action creators&quot; from step 4 can be further reduced:<p><pre><code> export const addTodo = text =&gt; ({ type: &#x27;ADD_TODO&#x27;, id: nextTodoId++, text, completed: false }); export const setVisibilityFilter = filter =&gt; ({type: &#x27;SET_VISIBILITY_FILTER&#x27;, filter}); export const toggleTodo = id =&gt; ({type: &#x27;TOGGLE_TODO&#x27;, id});</code></pre>

I think the funniest part is that the <i>total</i> number of meaningful lines in Redux source code is less than 250. Compare that to the supplied documentation with over 6,000 lines of Markdown.<p>If you have any FP background, this is really nothing innovative, more of a common sense kind of thing. With the main achievement being that it&#x27;s trivial enough and has nice documentation with examples so that mass JS programmers can actually grok it...<p>I&#x27;ve nothing against Redux, it&#x27;s a good idea but quite a bit overhyped is all.

Has anybody tried both Redux and Baobab? If so, do you think Redux is better and why? I&#x27;m using Baobab in a couple of projects and really liking it, but Redux from the tutorial I read seems to a bit too general to me. In Baobab you can subscribe components to their particular branches and only those components will re-render if the branches change.<p>In Redux, it seems to me, there&#x27;s no way you can do it, or at least nothing is provided out of the box. Am i correct?