But what about progressive web apps then? They’re red hot, they target mobile users and they are using client side rendering by default 
The prevalent architecture up until recently has been to use server-side rendering (SSR), which is when the browser fetches the page over HTTP/HTTPS and it immediately gets back a complete page with any dynamic data pre-rendered. Server-side rendering is nice because:
…
Client-side rendering (CSR) is when JavaScript runs in the browser and manipulates the DOM. The benefit of CSR is it offloads page updates to the client so that screen updates occur instantly when the user clicks, rather than waiting while the server is contacted for information about what to display. Thus, when data has changed after the initial page render, CSR can selectively re-render portions of the page (or reload the entire page) when new data is received from the server or following user interaction.
So what we speak about is technically going from SSR to CSR and then optimizing it by kinda going back to SSR with different server software, I know the hype but it does’t make much sense unless we already use NodeJS server side
@aadii104 ok sorry if it went off rails!
