Conversation

There’s a lot of talk about Next.js today but I want to highlight that

Hydrogen folks are providing invaluable feedback from using RSC in production, and their ongoing feedback is driving the refinement of RSC conventions: github.com/reactjs/rfcs/p

Quote Tweet

Sebastian Markbåge

@sebmarkbage

May 23, 2022

The great work done by @shuding_ and @huozhi on the RSC compiler is being reused for /app/ which will be how you adopt RSC in Next.js. Together with @Shopify we're also ironing out a few changes to RSC conventions. github.com/reactjs/rfcs/b

Show this thread

12:02 AM · May 24, 2022

Replying to

It’s a risk to build a framework on unproven tech. It is also an opportunity to contribute to it and help shape it, when you can afford to dedicate resources to trying & providing feedback. Waiting to see whether it works out might be wiser but misses out on that opportunity.

Replying to

and

Hey Dan, this is amazing! But what I'm just missing here is the manual parameters revalidation, in a similar way that was originally shown on the RSC presentation. IIRC Hydrogen has it too, but I don't know how I'd be implemented in the new Next or in a more vanilla-RSC

Replying to

and

In vanilla RSC you can see how it works in the demo. In Next, it will be added but the details are still being worked out. It might come after the initial release.

Replying to

and

What does "Server-centric routing with SPA-like behavior" mean. How do you manage page transitions with server routing in an SPA like hehavior? Don't you still need a client side router for that? Like why have server routing at all if your goal is to have a SPA behavior anyway?

Replying to

and

Thanks for the shout-out, Dan ❤️ Excited to iterate on RSC conventions even further and get Hydrogen out the door!