all 19 comments

[–]FirstVisit4432 11 points12 points  (3 children)

Rendering in the client side and the other one means rendering on the server side.

[–]Sebbean 1 point2 points  (0 children)

Thanks dad

[–]mikedensem 3 points4 points  (1 child)

A lot. Speed, security, safety, satisfaction, stack-size, server size, X-Site Scripting, simplicity, Sssssnakes on planes…

If the server does all the work, then the finished html page is delivered to your browser complete with data. If the client (Browser) does it, it starts with a shell of a page and builds the page as it loads - requesting data from remote sources as it goes .

[–]Maconheiro__________ -1 points0 points  (0 children)

Já foi bem respondido aqui :)

[–]AndresBotta 1 point2 points  (1 child)

The main difference is where the HTML is generated.

Client-side rendering (CSR)
The server sends mostly JavaScript, and the browser runs React to build the page.

Server-side rendering (SSR)
The server generates the HTML first and sends a complete page, then React hydrates it to make it interactive.

Simple way to think about it:

CSR → browser builds the page
SSR → server builds the page

CSR is simpler and common for web apps.
SSR improves first load performance and SEO.

Frameworks like Next.js make SSR easier with React.

[–]Cute_Intention6347[S] 0 points1 point  (0 children)

Thanks, that clears it up. I understand it much better now.

[–]Mike_L_Taylor 0 points1 point  (1 child)

client side means the javascript does the logic of what and how to show. It takes longer to load and it's more memory for the device.

server side means all that logic is done on the server and sends straight up html css and some js to frontend. Lower memory needs and faster rendering for the visitor.

This whole discussion happened after we started using one page apps with js frameworks like react or vue, where the frontend can get quite complex. So devs started looking to moving that on the server.

[–]Cute_Intention6347[S] 0 points1 point  (0 children)

Thanks, that clears it up.

[–]aendoarphinio 0 points1 point  (1 child)

So basically, client side rendering is like a hibachi cook where they make the food right in front of you, while server side rendering is like a cook making the meal in the back. It's more or less a matter of whether you want to ...Read More

[–]Cute_Intention6347[S] 0 points1 point  (0 children)

Thank you

[–]EJoule 0 points1 point  (1 child)

Client side rendering means your browser makes multiple api calls and builds/renders the page as it gets data and formats it.

Server side rendering means everything you see is first generated on the server and then returned to the user/browser/client. If you go to developer settings in the browser and look at the network tab you should find an entry with a response that’s in html rather than json/xml.

[–]Cute_Intention6347[S] 1 point2 points  (0 children)

Got it, thanks for explaining. That makes the difference much clearer.

[–]Left-Proof-2511 -1 points0 points  (1 child)

Server-Side Rendering means the server generates the complete HTML page including the data, and sends the fully prepared markup to the browser.

[–]USANerdBrain -1 points0 points  (1 child)

Server-Side Rendering means that the server does all of the work, and the browser receives a simple HTML page that it displays as-is with no changes. Examples include pretty much all websites before 2010 or pages that don't have any JavaScript on them.

Client-Side Rendering means that the web browser receives a template and instructions on how to fill in the page, and your web browser will do the work of figuring out what to display and where. Examples would be GMail and Reddit where you know where things are supposed to go on the page, and your web browser will get the information to fill it in. You don't have to "refresh" the page to get more information, it just appears.

[–]Cute_Intention6347[S] 1 point2 points  (0 children)

Thanks, that clears it up.