←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 1 comments | 02 Sep 25 06:57 UTC | HN request time: 0.277s | 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 #
1. port11 ◴[03 Sep 25 10:35 UTC] No.45114186[source]▶
This is only partially true. For example, with React Native even the core team now tells you to "just use Expo", as if relegating all responsibility to a project maintained by a for-profit that thinks 2 weeks is enough time to beta test a Major release.

It's also dismissive of market forces, i.e. developers have to pay bills and therefore are easier to hire if they know the skillset that is in wide use.

I've never worked or interviewed a single senior that wanted to use Next.