←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.474s | 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 #
christophilus ◴[02 Sep 25 10:07 UTC] No.45101028[source]▶
Second worst for me. I’ve used Sharepoint.
replies(6): >>45101349 #>>45101879 #>>45102199 #>>45102297 #>>45105540 #>>45112147 #
1. Sohcahtoa82 ◴[02 Sep 25 16:42 UTC] No.45105540[source]▶
To me, Sharepoint feels like it's not sure what it's supposed to be, so it tries to be everything, and so feature creep has run so rampant that it's just an utter mess with awful performance.
replies(1): >>45109122 #
2. christophilus ◴[02 Sep 25 21:11 UTC] No.45109122[source]▶
To me, Sharepoint feels like it was vibe coded by the first primitive coding agent, and then made worse over time.