<story><title>Show HN: I made React with a faster Virtual DOM</title><text>Hi! I made a React compatibility library for a Virtual DOM library (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aidenybai&amp;#x2F;million&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aidenybai&amp;#x2F;million&lt;/a&gt;).&lt;p&gt;The idea is to have much faster rendering (a compiler optimizes virtual DOM beforehand) while ensuring the same developer experience React provides.&lt;p&gt;This is very, VERY early stage, so be prepared for weird bugs &amp;#x2F; plugin incompatibility &amp;#x2F; etc. If you have any suggestions, I&amp;#x27;d be more than happy if you replied in a comment with it!&lt;p&gt;You can spin up the demo here &amp;gt;&amp;gt; &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackblitz.com&amp;#x2F;github&amp;#x2F;aidenybai&amp;#x2F;million-react-compat&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackblitz.com&amp;#x2F;github&amp;#x2F;aidenybai&amp;#x2F;million-react-compat&lt;/a&gt;</text></story><parent_chain><item><author>a13n</author><text>Is React rendering performance really a pain point worth solving? I&amp;#x27;ve never thought to myself &amp;quot;man I wish React would render faster&amp;quot;... It doesn&amp;#x27;t seem like this is whatsoever a bottleneck for our application (~1k unique components).&lt;p&gt;I feel like the main pain point with React is that routing, bundling, SSR, state management, etc. have to be painfully stapled together, and this is what frameworks like Next.js solve for.</text></item></parent_chain><comment><author>brundolf</author><text>It&amp;#x27;s not usually a problem, but if you&amp;#x27;re making an app that shows really large amounts of data it can become a bottleneck (I&amp;#x27;ve run into this personally). It also has less to do with number of unique components and more to do with the number of components on the screen at once, and the number that have to be (or end up) re-rendered on each update</text></comment>
<story><title>Show HN: I made React with a faster Virtual DOM</title><text>Hi! I made a React compatibility library for a Virtual DOM library (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aidenybai&amp;#x2F;million&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;aidenybai&amp;#x2F;million&lt;/a&gt;).&lt;p&gt;The idea is to have much faster rendering (a compiler optimizes virtual DOM beforehand) while ensuring the same developer experience React provides.&lt;p&gt;This is very, VERY early stage, so be prepared for weird bugs &amp;#x2F; plugin incompatibility &amp;#x2F; etc. If you have any suggestions, I&amp;#x27;d be more than happy if you replied in a comment with it!&lt;p&gt;You can spin up the demo here &amp;gt;&amp;gt; &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stackblitz.com&amp;#x2F;github&amp;#x2F;aidenybai&amp;#x2F;million-react-compat&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stackblitz.com&amp;#x2F;github&amp;#x2F;aidenybai&amp;#x2F;million-react-compat&lt;/a&gt;</text></story><parent_chain><item><author>a13n</author><text>Is React rendering performance really a pain point worth solving? I&amp;#x27;ve never thought to myself &amp;quot;man I wish React would render faster&amp;quot;... It doesn&amp;#x27;t seem like this is whatsoever a bottleneck for our application (~1k unique components).&lt;p&gt;I feel like the main pain point with React is that routing, bundling, SSR, state management, etc. have to be painfully stapled together, and this is what frameworks like Next.js solve for.</text></item></parent_chain><comment><author>aporetics</author><text>Well, let’s look at it from a different angle; not the angle of the user or the developer, but as a matter of computational work and the energy consumed by that work. In a single application or even the life of an application all it might be negligible. But when does it not become negligible? What if react adopted the change and every react app What about for every react app in use suddenly used a fraction less computational power each render?&lt;p&gt;And is it just a monetary cost?&lt;p&gt;Yes, if energy use is your primary concern there are easier ways to reduce it. But in the above context it seems clear that you should take your gains where you can get them.</text></comment>