News for hackers. Stuff that matters.
Re:Next.js 10.2 by eyelidlessness on Wednesday April 28, 2021 @04:43PM (#26973955)
This isn’t so much about 10.2, but about Next’s plans/roadmap for static sites, particularly whether there are plans to provide official support for partial hydration.

I like a lot of what Next brings in terms of DX polish. But I ultimately decided not to use it for recent projects, where the majority of the content is truly static. Next sends this content in HTML, then sends it again in JS. This not only adds unnecessary page weight, it also increases the uncanny valley before TTI.

The current solution to this in Next is to mark an entire page as non-interactive. This means a page will send either no JS at all, or all of it. This isn’t ideal.

There are several experimental projects exploring partial hydration with Next, but without official support they’re risky. There are also emerging projects like Astro providing similar functionality to Next with partial hydration as a core feature.

I’d imagine the most obvious way to achieve something similar in Next will be SSG with React Server Components, but who knows when that will be stable.

Anyway, curious if Vercel has anything to share on the topic.

Re:Next.js 10.2 by leerob on Wednesday April 28, 2021 @07:27PM (#26975523)
> I’d imagine the most obvious way to achieve something similar in Next will be SSG with React Server Components, but who knows when that will be stable.

Sooner than you might think!

Re:Next.js 10.2 by eyelidlessness on Wednesday April 28, 2021 @09:18PM (#26976370)
That’s cool! On a similar note I’m curious if you’ve encountered Astro[1] and if you have any thoughts on where Next/Astro overlap and where they might not.

1: astro.build