<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>DeathArrow</author><text>There&amp;#x27;s room for both approaches.&lt;p&gt;Some people can use pre-made UI components while others can have them tailor-made to better fit the case.&lt;p&gt;I, as a programmer, have a tough work to design UI components that fit well together, and of course I don&amp;#x27;t do as a good job as someone trained to do this.&lt;p&gt;So, I rather reuse components done by others if the project I am working on does not have a budget for UI specialists as can happen to a lot of projects.</text><parent_chain><item><author>davnicwil</author><text>&amp;gt; Untold amounts of human effort are exhausted globally every day on rebuilding identical components for web apps. This should not be the case. The UI community should standardize namings and structures for common components.&lt;p&gt;It&amp;#x27;s so tempting to think of all the efficiency that could be gained if we&amp;#x27;d stop replicating the same work and just all decide how to do things &amp;#x27;right&amp;#x27;, unfortunately though this isn&amp;#x27;t how the best results are achieved.&lt;p&gt;This is fundamentally a conversation about markets - in this case for ideas. Lots of parallel work is done in a distributed manner, much of it is wasted, but because of the competition between and combination of different ideas, you get emergent results that are really finely tuned to what people actually want in practice.&lt;p&gt;Top down planning won&amp;#x27;t get you this. You&amp;#x27;ll have less waste, to be sure, but you&amp;#x27;ll also have inferior results.</text></item></parent_chain></comment><story><title>Open UI</title><url>https://open-ui.org/</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>_bxg1</author><text>The web has traditionally followed a pattern where people are left to try out new things themselves, experiment with ideas, have a competitive marketplace of libraries and frameworks, and then once there&amp;#x27;s a consensus the selected approach gets enshrined and implemented as a browser standard that everyone can use. This happened with DOM selection and XHR fetching (jQuery), with promises, with list comprehensions, with modules syntax (ES Modules). It&amp;#x27;s time it happened with reactive DOM rendering.</text><parent_chain><item><author>davnicwil</author><text>&amp;gt; Untold amounts of human effort are exhausted globally every day on rebuilding identical components for web apps. This should not be the case. The UI community should standardize namings and structures for common components.&lt;p&gt;It&amp;#x27;s so tempting to think of all the efficiency that could be gained if we&amp;#x27;d stop replicating the same work and just all decide how to do things &amp;#x27;right&amp;#x27;, unfortunately though this isn&amp;#x27;t how the best results are achieved.&lt;p&gt;This is fundamentally a conversation about markets - in this case for ideas. Lots of parallel work is done in a distributed manner, much of it is wasted, but because of the competition between and combination of different ideas, you get emergent results that are really finely tuned to what people actually want in practice.&lt;p&gt;Top down planning won&amp;#x27;t get you this. You&amp;#x27;ll have less waste, to be sure, but you&amp;#x27;ll also have inferior results.</text></item></parent_chain></comment><story><title>Open UI</title><url>https://open-ui.org/</url></story>