Next.js: Document why you have server side rendering
I'm missing a FAQ entry explaining why next.js opted for server side rendering and not on client side. This would help me evaluating frameworks.
A detailed and/or opinionated comparison between these two and the reasons why SSR has been picked would be awesome.
binarykitchen
All 2 comments
not on client side
Next.js does both, SSR and CSR.
First request is rendered server side and then when client JS code loads on the browser is "rendered" client side (the " are because React try to avoid rendering again and instead it just starts to listen events and other few things). Then when you navigate to another page it loads the required JS code and do the navigation and render client side as an SPA.
To understand why SSR I personally recommend you to read https://rauchg.com/2014/7-principles-of-rich-web-applications#server-rendered-pages-are-not-optional.
sergiodxa
on 6 Apr 2018
Ok, maybe we can close this issue? @binarykitchen
joshuaquek
on 26 Apr 2018
Related issues
acanimal
路
74Comments
timneutkens
路
250Comments
nickredmark
路
60Comments
ematipico
路
66Comments
Knaackee
路
122Comments
Most helpful comment
First request is rendered server side and then when client JS code loads on the browser is "rendered" client side (the
"are because React try to avoid rendering again and instead it just starts to listen events and other few things). Then when you navigate to another page it loads the required JS code and do the navigation and render client side as an SPA.To understand why SSR I personally recommend you to read https://rauchg.com/2014/7-principles-of-rich-web-applications#server-rendered-pages-are-not-optional.