Recently, RSC has emerged as a hot topic in web development...
It can be likened to a chef preparing semi-cooked food and giving it to the customer, who then simply finishes it at the table. In essence, the chef handles the complex tasks, while the customer only needs to do simple cooking... The chef doesn't need to fully prepare the dish, and the customer doesn't have to do everything from scratch...
Existing SSR (Server Side Rendering - rendering the screen on the server and sending the completed HTML to the browser) can be compared to a restaurant where you order, the chef prepares the dish, and serves it directly to you.
Then, CSR (Client Side Rendering - rendering everything on the browser) can be compared to a self-service where the customer goes to the kitchen, gets the ingredients, and cooks.
Even though server components run on the server, it doesn't necessarily mean they perform screen rendering (SSR). Server components can process data or prepare parts of the HTML and collaborate with client components... In other words... It combines the advantages of SSR and CSR, but if not done properly, it could end up combining the disadvantages. It's a topic that is still under debate and doesn't have an easy conclusion. Personally, I don't like these fusion-like... ambiguous concepts, but since the recent trend seems to be heading in this direction, it seems to prove that I am not becoming obsolete. .ㅜㅜ;
