6 ms·
I think the author didn’t really read about RSC in NextJS, which is what they’re mostly confused about. There’s a ton of documentation about it as well. However
by haburka 2y ago
I think the author didn’t really read about RSC in NextJS, which is what they’re mostly confused about. There’s a ton of documentation about it as well. However it’s immature.
To the authors credit, the community is way too excited about RSC and the documentation on NextJS suggests you should really be using it but it’s absolutely half baked. Use the Pages router for now.
RSC is a new paradigm that you would probably be better off to ignore until its a few years old. Just like many things in frontend and tech in general. Don’t use the shiny new thing unless you wanna be cut on the bleeding edge.
- mrwyndham 2y agoWhere is the documentation? The vercel docs don't cover the things op is mentioning very well if at all. RSC isn't a problem it is next implementation of it that is. Understanding SSR,SSG,CSR etc is obvs where people get unstuck and that's fine but the api (use client, use server) and the arbitrary limitations on whatcan and cant be done serverside make this framework he'll to deal with I think next.js is in danger of not existing. Openai moved to remix. I am moving to Astro many people I know are considering moving
- leerob 2y agoIt's worth noting this post is a year old. I can't remember exactly if this was mentioned in the docs at that time, but it is now: https://nextjs.org/docs/app#how-can-i-set-cookies https://nextjs.org/docs/app#how-can-i-set-cookies. It's possible this post influenced us making the docs better last year.