<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>skrebbel</author><text>&lt;i&gt;(Marginally related rant)&lt;/i&gt;&lt;p&gt;I love React, but so far I&amp;#x27;ve been a bit underwhelmed by the ecosystem of components that has sprung up. I hope that this site will help.&lt;p&gt;A lot of the components are stuff that aren&amp;#x27;t really UI elements, but rather add magic to other UI elements or even do something completely unrelated to the UI.&lt;p&gt;I mean, I&amp;#x27;ve seen routers written as React components![1] Wtf? Why is it an advantage to express a route as XML-like JSX? Why put it in a virtual DOM? That&amp;#x27;s just waiting for unexpected side-effects to happen. I can imagine that a lean, to-the-point router is a good combination with React but components are for &lt;i&gt;UI widgets&lt;/i&gt;, not for configuration.&lt;p&gt;I feel like this is the same mistake as the everything-in-XML hype of the early 21st century (Spring, anyone?), or the everything-as-a-DSL hype in early Scala (with clear, descriptive operators such as ~~=, $%% and of course &amp;amp;^), or the current hype in C#-o-world to package web assets into NuGet packages (jquery.dll - seriously?). Just because you &lt;i&gt;can&lt;/i&gt; put it in a component, doesn&amp;#x27;t mean that you &lt;i&gt;should&lt;/i&gt;.&lt;p&gt;Behavioral features for components (e.g. infinite-scrolling or tooltip triggers) are well distributed as a mixin. Stuff not directly related to UI widgets should just be vanilla JavaScript. Asset libraries should be asset libraries.&lt;p&gt;What I expect from open source components is UI elements. Color pickers, fancy dropdown selects, login widgets, form elements with pluggable validation maybe (but the validation logic shouldn&amp;#x27;t be components). Notably, I&amp;#x27;d love an ecosystem of UI frameworks ala Bootstrap or Foundation to spring up around React, and it appears that this is happening.&lt;p&gt;(Sidenote, if there&amp;#x27;s one development we &lt;i&gt;do&lt;/i&gt; need, then it&amp;#x27;s a clear React-authors-condoned way to couple (parameterized) CSS with React components, so that we can really distribute self-contained components including style. A development like that would also help focus the React component ecosystem on what it should be about: UI widgets.)&lt;p&gt;[1] Random example: &lt;a href=&quot;https://github.com/rackt/react-router#whats-it-look-like&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rackt&amp;#x2F;react-router#whats-it-look-like&lt;/a&gt; - seriously, what were they thinking?</text><parent_chain></parent_chain></comment><story><title>React Components</title><url>http://react-components.com/</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>blablabla123</author><text>Interesting... Actually last week I stumbled upon react-bootstrap. After all I wasn&amp;#x27;t enthusiastic to use it yet, because I wonder whether it interfers with the regular bootstrap. (Right now the app I work on is only partially implemented in React.)</text><parent_chain></parent_chain></comment><story><title>React Components</title><url>http://react-components.com/</url></story>