<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>hardwaregeek</author><text>Redux is a very good example of this. If you watch the original talk or just understand primitives like Observables, you can realize that Redux almost isn&amp;#x27;t a library. It&amp;#x27;s basically a pattern. Where libraries are actually required is when you connect Redux to React, or need async actions. But even then it&amp;#x27;s not super hard to see how they work.</text><parent_chain><item><author>jjcm</author><text>Presentation is amazing here.&lt;p&gt;That said, I recently wrote a webcomponent based router and I was surprised at how easy it was to get to a very usable point at such a minimal amount of code. All too often I get in the loop of just `npm i`&amp;#x27;ing whatever it is I need, even if the functionality I really need is just a tiny subset of whatever huge library I&amp;#x27;m importing.&lt;p&gt;Rodrigo&amp;#x27;s right that something like this helps you understand React and how to contribute to the codebase, but I think it goes further than that - it lets you understand that the library isn&amp;#x27;t magic. It gives you the confidence you need to think that maybe you don&amp;#x27;t need that full 560kb library.</text></item></parent_chain></comment><story><title>Build Your Own React</title><url>https://pomb.us/build-your-own-react/</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>rajeev-k</author><text>&amp;gt; &lt;i&gt;webcomponent based router&lt;/i&gt;&lt;p&gt;Routers can be (and should be, IMO) written to be independent of UI component libraries such as React and webcomponents. See an example here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Rajeev-K&amp;#x2F;mvc-router&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Rajeev-K&amp;#x2F;mvc-router&lt;/a&gt; You can use it with React---and in some ways it works better than react-router.</text><parent_chain><item><author>jjcm</author><text>Presentation is amazing here.&lt;p&gt;That said, I recently wrote a webcomponent based router and I was surprised at how easy it was to get to a very usable point at such a minimal amount of code. All too often I get in the loop of just `npm i`&amp;#x27;ing whatever it is I need, even if the functionality I really need is just a tiny subset of whatever huge library I&amp;#x27;m importing.&lt;p&gt;Rodrigo&amp;#x27;s right that something like this helps you understand React and how to contribute to the codebase, but I think it goes further than that - it lets you understand that the library isn&amp;#x27;t magic. It gives you the confidence you need to think that maybe you don&amp;#x27;t need that full 560kb library.</text></item></parent_chain></comment><story><title>Build Your Own React</title><url>https://pomb.us/build-your-own-react/</url></story>