Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

nextjs.org

Post reply on HN
Print view View original

11–20 of 123 posts

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#11

Post by realce »

leerob wrote: post #2

Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.

Am I correct thinking this will help create a simpler integration with - just hypothetically - Prisma calls that are dependent on app auth states in a single page? Replacing auth providers and moving them into Layouts?

Daily user, very excited!

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#12

Post by rs_rs_rs_rs_rs »

leerob wrote: post #2

Lee from Vercel, happy to answer questions about the RFC or future plans for Next.js. This RFC has been years in the making – and I'm pretty happy with where we've landed.

>happy to answer questions about the RFC

Would love to hear about the parts of the RFC where you guys took some inspiration from Remix!

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#14

Post by pier25 »

reilly3000 wrote: post #10

Could a smart person please compare and contrast this RFC and the ideas of remix.run?

According to Ryan Florence (Remix's creator) they are "ripping features straight from Remix".

https://twitter.com/ryanflorence/status/1528859776930545665

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#16

Post by nullcipher »

austinkhale wrote: post #3

We're irrationally excited about this internally and we're super happy with how the Vercel team has continued to push Next.js forward. Thank you! We're using a version of the persistent layout pattern Adam Wathan [blogged about]( https://adamwathan.me/2019/10/17/persistent-layout-patterns-... ) but having first-class support for this paradigm will be awesome.

"irrationally excited" - what does this phrase mean? that there is no basis for your excitement? sounds so cheesy

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#17

Post by freedomben »

I'm excited to see the wheels turning, but it feels a bit like the best feature of Next.js IMHO (SSG) is going to get more difficult, or possibly become unusable. A deprecation feels incoming. It could be confirmation bias as I've been a little worried about that for awhile since people using SSG aren't as likely to buy cloud services, so there's some incentive misalignment there, but ever since the Image component was only supported with SSR it's felt like SSG was going to either become less usable or disappear. Am I the only person who loves that feature? It really revolutionized how I approach web dev and enlarged my imagination of what was possible, so there's definitely some emotional attachment for me :-)

Am I correct about SSG's future?

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#19

Post by dimgl »

reilly3000 wrote: post #10

Could a smart person please compare and contrast this RFC and the ideas of remix.run?

It's almost an exact copy aside from the conventions and names. It very much _is_ Remix. This is pretty wild. It also brings one of my gripes from Remix: parallel fetching. In practice it makes sense, but at times there needs to be a way to fetch data on a parent route first so that child routes don't fetch again. I'm sure Vercel will find a way to solve this.

Re: Next.js Layouts RFC: Nested routes and layouts, designed for Server Components

#20

Post by madjam002 »

pier25 wrote: post #14
reilly3000 wrote: post #10

Could a smart person please compare and contrast this RFC and the ideas of remix.run?

According to Ryan Florence (Remix's creator) they are "ripping features straight from Remix". https://twitter.com/ryanflorence/status/1528859776930545665

So we need to give credit now to every little bit of inspiration we get when coming up with new features and ideas?

Not really sure what the problem is here.

Post reply on HN