<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>tlrobinson</author><text>I like the elegant simplicity of Redux, but it&amp;#x27;s so low-level and definitely feels like people are still figuring the &amp;quot;right&amp;quot; way to do a lot of things.&lt;p&gt;I tweeted my feelings on this last week:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    2015: reflux flummox redux marty alt fluxible…
    2016: redux-actions redux-act redux-forms redux-promise redux-ui…
&lt;/code&gt;&lt;/pre&gt;
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;tlrobinson&amp;#x2F;status&amp;#x2F;717258992989306880&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;tlrobinson&amp;#x2F;status&amp;#x2F;717258992989306880&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Two Weird Tricks with Redux</title><url>http://jlongster.com/Two-Weird-Tricks-with-Redux</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>BinaryIdiot</author><text>I don&amp;#x27;t know much about Redux but these tricks seem like they should be less trick and more re-worked flow.&lt;p&gt;For the first one, if a burger is meant to be consumed differently than fries (serial versus parallel) they why are they using the same mechanism with the burger having a hacked on predicate , service type, dispatch, etc? Why wouldn&amp;#x27;t the burger just have a workflow that makes sense for how its invoked? For instance if the burger is tied to the UI and a backend request that must happen one at a time then the UI would disallow or provide a way of queueing which I guess this sorta supports but it seems forced and doesn&amp;#x27;t look like a normal flow.&lt;p&gt;The second part, ignoring async responses. I don&amp;#x27;t understand this part. Why can&amp;#x27;t you just replace your state and drop the existing handlers so nothing async from the previous state occurs? Does redux just not support this out of the box or is the author doing something very edge-case-y?&lt;p&gt;When I don&amp;#x27;t want to handle an async response anymore I remove the handle&amp;#x27;s association with the event it was going to handle. It works like this in native DOM, jQuery, even my own bias data point: msngr. But I&amp;#x27;m curious why wouldn&amp;#x27;t redux be able to handle the same case?</text><parent_chain></parent_chain></comment><story><title>Two Weird Tricks with Redux</title><url>http://jlongster.com/Two-Weird-Tricks-with-Redux</url></story>