←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 2 comments | 02 Sep 25 06:57 UTC | HN request time: 0.41s | source
Show context
YuukiRey ◴[02 Sep 25 10:04 UTC] No.45101009[source]▶
I 100% agree. I've ran into the same issues, and I would never use Next.js for anything, and I will encourage every team at work to use something else.

In general Next.js has so many layers of abstraction that 99.9999% of projects don't need. And the ones that do are probably better off building a bespoke solution from lower level parts.

Next.js is easily the worst technology I've ever used.

replies(16): >>45101028 #>>45101139 #>>45101375 #>>45101378 #>>45102069 #>>45102103 #>>45102427 #>>45102810 #>>45102903 #>>45103225 #>>45104004 #>>45104045 #>>45105250 #>>45110734 #>>45112201 #>>45126685 #
motorest ◴[02 Sep 25 12:12 UTC] No.45102069[source]▶
> I 100% agree. I've ran into the same issues, and I would never use Next.js for anything, and I will encourage every team at work to use something else.

Things will get far worse before they get better. Right now, online courses such as the ones in PluralSight are pushing Next.js on virtually all courses related to React. I have no idea what ill-advised train of thought resulted in this sad state of affairs but here we are.

replies(1): >>45102683 #
felipeccastro ◴[02 Sep 25 13:12 UTC] No.45102683[source]▶
The train of thought is “what is everyone using? I’ll use that too”
replies(4): >>45103142 #>>45103151 #>>45103593 #>>45114186 #
motorest ◴[02 Sep 25 14:29 UTC] No.45103593[source]▶
> The train of thought is “what is everyone using? I’ll use that too”

I'm not so sure about that. We're seeing Next.js being pushed as the successor of create-react-app even in react.dev[1], which as a premise is kind of stupid. There is something wrong definitely going on.

[1] https://react.dev/learn/creating-a-react-app

replies(2): >>45103689 #>>45103721 #
whstl ◴[02 Sep 25 14:36 UTC] No.45103689[source]▶
It was interesting handling frontend interviews recently.

We do a 30-min tops exercise where you create a React project to show how to use useState and useEffect, etc. I help with whatever command they want to use and allow Google/ChatGPT.

More than half of the candidates had no idea how to use React without Next.js, and some argued it was impossible, even after I told them the opposite.

replies(2): >>45104339 #>>45107612 #
1. nikole9696 ◴[02 Sep 25 19:06 UTC] No.45107612[source]▶
This surprises me a lot. I spin up new react apps with vite often to replicate issues with 3rd party libs we use. Like how do they not know you can just spin something up over on CodePen or CodeSandbox and there's not a hint of a server side paradigm required? (sure, vite has a little server but you don't really need to know anything about it)
replies(1): >>45110217 #
2. whstl ◴[02 Sep 25 22:59 UTC] No.45110217[source]▶
Some devs have worked exclusively in feature mills where expectations are rock bottom and some senior setups the project for them. When recruiters don't filter them, a basic React test has to.