Re:You don't need Next.js – Why we migrated from Next to React
by hu3 on Wednesday January 01, 2025 @01:27PM
(#42567969)
> You intentionally cannot access the raw request object. However, you can access headers and cookies through server-only functions. You can also set cookies.
> Layouts do not rerender. They can be cached and reused to avoid unnecessary computation when navigating between pages. By restricting layouts from accessing the raw request, Next.js can prevent the execution of potentially slow or expensive user code within the layout, which could negatively impact performance.
I don't like this limiting "I know best what's good for you" attitude in my tooling.
Yes limits are desirable to avoid footguns but this seems like too dumbed down of a restriction for little gain.
Re:You don't need Next.js – Why we migrated from Next to React
by citizenpaul on Friday January 03, 2025 @08:18PM
(#42591336)
Do some people prefer using filesystem routing? I don't think I've used it before but it sounds clunky.
If filesystem routing isn't something you enjoy, Next.js probably isn't the right tool for you.