Content
@
0 reply
0 recast
0 reaction
greg
@gregfromstl
Next devs: How much of your frontend do you render server-side? In the past few weeks I’ve gone from hardcore SSR advocate to confused/questioning what I thought was the best way to do things. From what I’ve seen others are starting to feel the same
6 replies
1 recast
5 reactions
Justin Hunter
@polluterofminds
Since the move to app router, I'm less and less excited about Next.js in general. So, I guess the answer is still a lot SSR, but looking for alternatives.
1 reply
0 recast
0 reaction
matt 💭
@matthewmorek
SSR-first where possible, then ISR. I’m not an advocate, I just like delivering performant websites. As for apps, that may be a bit different due to how I like to deliver the UX, in which case some SSR and some CSR with rehydration.
0 reply
0 recast
0 reaction
Noclue4u
@noclue4u
I’ve just launched a project where everything was on the server that could. I started when server actions where not a thing yet, so I possibly could get an even more higher coverage. It’s a different mindset and approach to building projects. All components are server comps and you use client on interactivity.
1 reply
0 recast
1 reaction
SonOfMosiah
@sonofmosiah.eth
@thesyntaxninja
0 reply
0 recast
0 reaction
Sohey.base.eth
@sohey.eth
SSR first then only using client components on interactive elements
0 reply
0 recast
0 reaction
Parker Esmay 🎩
@thesyntaxninja
I typically get some initial data with RSC and hand it over to the client for revalidation, infinite scroll, etc. I still don't fully trust revalidation with Next. Not hardcore about trying to keep everything server side. I keep things snappy with prefetch hooks and proper cache management using RQ
0 reply
0 recast
0 reaction
