<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Server-Components on Commentary of Takao</title><link>https://takao.blog/en/tags/server-components/</link><description>Recent content in Server-Components on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/server-components/index.xml" rel="self" type="application/rss+xml"/><item><title>React Server Components: The Future of Web Rendering</title><link>https://takao.blog/en/web/react-server-components/</link><pubDate>Mon, 08 Jan 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/react-server-components/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post React Server Components: The Future of Web Rendering" /&gt;&lt;p&gt;React Server Components (RSC) represent a paradigm shift in how React applications render. Components run exclusively on the server, sending zero JavaScript to the client. This is not the same as Server-Side Rendering (SSR), which renders components on the server but still sends all the JavaScript for them to the client for hydration. RSC produces a special serialized format — the RSC payload — that the React reconciler on the client uses to reconstruct the component tree without executing the component code.&lt;/p&gt;</description></item></channel></rss>