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

Next.js App Router Update

nextjs.org

Post reply on HN
Print view View original

21–30 of 93 posts

Re: Next.js App Router Update

#21

Post by qudat »

aosaigh wrote: post #2

I really want to like Next.js but as a recent adopter (within the last year) I’m not sure I’m going to stick with it. I find the “new” way to write Next apps incredibly confusing. Everything is now a mix of server and client and there’s so much rendering complexity. Im sure for big ambitious companies this focus on performance is great, but I find that it greatly compromises developer experience. I’ve also found the…

I fear next.js has been infected, like many other incredibly successful projects, by the ever expanding feature-set to match the ever expanding popularity.

We have seen it all before and will continue to see it again.

> Any successful project will start by doing one thing, well, but end up doing many things, poorly.

https://bower.sh/bowers-law

Re: Next.js App Router Update

#22

Post by re-thc »

sroussey wrote: post #8

Vercel as a hosting provider is almost purposely slow (at least on the free tier) for app router based sites. RSC files in particular take 500ms to 2000ms to start serving those static files.

App router itself is slow (slower than page router).

Re: Next.js App Router Update

#23

Post by jjdeveloper »

jer0me wrote: post #20
TechBro8615 wrote: post #18

Next and React have gotten way too complicated. I don't want to read twelve pages of documentation to understand how to understand the rest of the documentation. I've been coding in React for 6 years and in Next for 3 years. My next project will be in Vue.

Your nuxt project will be Vue?

good correction

Re: Next.js App Router Update

#24

Post by evantbyrne »

slimebot80 wrote: post #16
sroussey wrote: post #8

Vercel as a hosting provider is almost purposely slow (at least on the free tier) for app router based sites. RSC files in particular take 500ms to 2000ms to start serving those static files.

lots of free tiers have slow start up times when an app has been idle (eg: heroku and render) Not 100% sure if this is what is causing that on Vercel, but seems fair to me for free tiers?

People definitely get what they pay for. Heroku was and still is notoriously slow, charging a massive premium for convenience. I'm obviously biased because I built a CD service for AWS, but I strongly believe that when a hosting service doesn't advertise what hardware resources you are actually getting, it's a trap.

Re: Next.js App Router Update

#25

Post by aarpmcgee »

I have found that it is pretty difficult to find what I'm looking for when searching for articles/issues that relate in any way to the Next router. "App router" and "pages router" were two of the most ungooglable and generic name they could have chosen. Suddenly it is much more difficult to find what I'm looking for in the ecosystem.

Re: Next.js App Router Update

#26

Post by re-thc »

aosaigh wrote: post #2

I really want to like Next.js but as a recent adopter (within the last year) I’m not sure I’m going to stick with it. I find the “new” way to write Next apps incredibly confusing. Everything is now a mix of server and client and there’s so much rendering complexity. Im sure for big ambitious companies this focus on performance is great, but I find that it greatly compromises developer experience. I’ve also found the…

Dev mode is also a lot slower in app router (well so is production). HMR feels like a crawl even on a fast machine.

Re: Next.js App Router Update

#27

Post by leerob »

sroussey wrote: post #8

Vercel as a hosting provider is almost purposely slow (at least on the free tier) for app router based sites. RSC files in particular take 500ms to 2000ms to start serving those static files.

The page load performance of a site on Vercel's free and paid tier should be the same. Both would be using Vercel's Edge Network and possible a Vercel Function if dynamically rendered. As mentioned in the post, we're working to improve loading performance in general with the Next.js App Router.

Re: Next.js App Router Update

#28

Post by re-thc »

slimebot80 wrote: post #16
sroussey wrote: post #8

Vercel as a hosting provider is almost purposely slow (at least on the free tier) for app router based sites. RSC files in particular take 500ms to 2000ms to start serving those static files.

lots of free tiers have slow start up times when an app has been idle (eg: heroku and render) Not 100% sure if this is what is causing that on Vercel, but seems fair to me for free tiers?

It's backed by lambda that has cold start. Don't think that part has to do with free tiers.

Re: Next.js App Router Update

#29

Post by leerob »

_nkl1 wrote: post #12

I’ve recently started working with NextJs and absolutely loving it so far. However, with adopting the App Router there is a big looming question - what happens with frontend state/query management libraries like react-query/trpc? So far, I’ve seen unergonomic solutions that require the developer to manually hydrate the frontend. Hopefully, over the next few months we discover a solution that “just works”, so we can w…

You can continue to use state management libraries that take advantage of React hooks or other client-side logic inside of client components. Alternatively, you can move state management entirely to the server. That could be state in your database, URL state, or something else.

Re: Next.js App Router Update

#30

Post by reducesuffering »

satvikpendem wrote: post #6
8f2ab37a-ed6c wrote: post #3

Earlier quoted context omitted.

What's a full-stack TypeScript-based alternative that's good enough for most of us? I constantly bump into the complexity of NextJS myself, but so far I've powered through the pain.

Vite with trpc? I personally don't use the backend functionality of NextJS at all, I have my own backend (in Rust but I'd do the same in Node as well) that communicates via GraphQL to the frontend in NextJS, it's pretty nice.

What are you doing with trpc if your backend is in Rust? trpc is typescript to typescript
Post reply on HN