←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 1 comments | | HN request time: 0s | 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 #
motorest ◴[] 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 ◴[] No.45102683[source]
The train of thought is “what is everyone using? I’ll use that too”
replies(4): >>45103142 #>>45103151 #>>45103593 #>>45114186 #
koonsolo ◴[] No.45103151{3}[source]
This coupled with the fact that "web development" now means anything going from a content rich website like a blog, towards some e-shop, all the way to complex applications like ux design, video editing, etc.

It's pretty absurd to have such a broad range of web solutions, and think the same solution can cover everything.

replies(1): >>45104359 #
fragmede ◴[] No.45104359{4}[source]
Why? Microsoft's GUI framework as well as Apple's covered plenty of use cases before the rise of the web browser.
replies(1): >>45105727 #
koonsolo ◴[] No.45105727{5}[source]
Then why did HTML became so popular if win32 or MFC were so great?
replies(2): >>45105799 #>>45112468 #
fragmede ◴[] No.45105799{6}[source]
Because it solved different problems. CSS is terrible, but deployment simplicity and distribution channel were more powerful than how shitty HTML is for making GUIs. The fact that MFC was owned by Microsoft didn't help either.
replies(1): >>45106402 #
1. koonsolo ◴[] No.45106402{7}[source]
Why would you make GUI's with HTML? Its main use was for content, not applications. Hyper Text Markup Language.

So you agree both solve different problems. Well, those are 2 use cases of front-end right now.