<story><title>Next.js 12</title><url>https://nextjs.org/blog/next-12</url></story><parent_chain><item><author>leotaku</author><text>I&amp;#x27;m personally curious how the Next is able to achieve the claim of &amp;quot;zero client-side JavaScript&amp;quot; mentioned here[1] using react server components? It just doesn&amp;#x27;t seem to make sense to me, and the HN clone example and my barebones test project also clearly still load about 74.2 KB of JavaScript. Is the claim supposed to mean that the server components won&amp;#x27;t require additional JS, or maybe that they won&amp;#x27;t need to execute any client-side JS to be fully rendered?&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;docs&amp;#x2F;advanced-features&amp;#x2F;react-18#react-server-components&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;docs&amp;#x2F;advanced-features&amp;#x2F;react-18#react-ser...&lt;/a&gt;</text></item><item><author>leerob</author><text>Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I&amp;#x27;m extremely excited for the new Rust compiler.</text></item></parent_chain><comment><author>krall12</author><text>I think it means that any page that only renders server components can just push the built html to the browser. If there were to be client components, like an upvote button, react would be required for that to hydrate the DOM.&lt;p&gt;It’s very similar to what Astro is doing. Only adding the JS if it’s actually necessary.</text></comment>
<story><title>Next.js 12</title><url>https://nextjs.org/blog/next-12</url></story><parent_chain><item><author>leotaku</author><text>I&amp;#x27;m personally curious how the Next is able to achieve the claim of &amp;quot;zero client-side JavaScript&amp;quot; mentioned here[1] using react server components? It just doesn&amp;#x27;t seem to make sense to me, and the HN clone example and my barebones test project also clearly still load about 74.2 KB of JavaScript. Is the claim supposed to mean that the server components won&amp;#x27;t require additional JS, or maybe that they won&amp;#x27;t need to execute any client-side JS to be fully rendered?&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;docs&amp;#x2F;advanced-features&amp;#x2F;react-18#react-server-components&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nextjs.org&amp;#x2F;docs&amp;#x2F;advanced-features&amp;#x2F;react-18#react-ser...&lt;/a&gt;</text></item><item><author>leerob</author><text>Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I&amp;#x27;m extremely excited for the new Rust compiler.</text></item></parent_chain><comment><author>leerob</author><text>You can read more here on the original RSC announcement: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;reactjs.org&amp;#x2F;blog&amp;#x2F;2020&amp;#x2F;12&amp;#x2F;21&amp;#x2F;data-fetching-with-react-server-components.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;reactjs.org&amp;#x2F;blog&amp;#x2F;2020&amp;#x2F;12&amp;#x2F;21&amp;#x2F;data-fetching-with-react...&lt;/a&gt;. RSC are still experimental, and as mentioned, this demo has some client-side functionality (upvotes).</text></comment>