←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 1 comments | | HN request time: 0.199s | source
Show context
YuukiRey ◴[] 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 #
jimbokun ◴[] No.45102810[source]
Sounds like Javascript's answer to Spring.
replies(2): >>45106059 #>>45106660 #
thr0w ◴[] No.45106059[source]
That would be Nest, not Next. A true abomination.
replies(1): >>45108939 #
mablopoule ◴[] No.45108939[source]
I'm a bit surprised at reading that. I've tried both, Next left a bad taste in my mouth, but Nest was kinda neat. Didn't used it for anything too complicated though, so I'm curious about what sort of grievances people have against Nest.
replies(1): >>45112244 #
1. Aeolun ◴[] No.45112244[source]
Something, something enterprise software. I find its dependency injection harder to reason about.