Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js is infuriating

blog.meca.sh

Post reply on HN
Print view View original

461–470 of 602 posts

Re: Next.js is infuriating

#461

Post by 9rx »

fragmede wrote: post #456
9rx wrote: post #451

Earlier quoted context omitted.

Why would one random part of the interview disallow ChatGPT when it is otherwise accepted for answering other random React minutiae?

Because humans have to interact with other humans in conversations, and if you can't read social cues as to when something is and isn't acceptable, you're boned. I have trouble with that, so it's not surprising to me when others do as well. When you're in a work meeting, do you just put ChatGPT up on one laptop and Claude on another and just sit back for 30 minutes to an hour?

It was deemed acceptable to use ChatGPT to discover the minutiae of useState and useEffect. What is special about createRoot that makes it off limits?

Re: Next.js is infuriating

#462

Post by turtlebits »

zarzavat wrote: post #122
mvdtnz wrote: post #63

Earlier quoted context omitted.

> Otherwise, just tread the well-trod path and stick to either a react-vite SPA or something like Rails doing ordinary SSR. Just write your SPA the grown up way. Write your APIs in a language and framework well suited to such work (pick your poison, Rails, Spring, whatever Microsoft is calling this year's .NET web technology). And write your front-end in Typescript. There's absolutely no reason to tightly couple your…

I don't agree. Having front-end and backend in the same language is so convenient I would never go back to doing it the old way. I'd rather compile the frontend to WASM than introduce a mismatch. I used to use Django and there were so many issues that arose from having to duplicate everything in JS and Python.

What about HTML? Are you writing HTML via JS - if not you're already writing multiple languages.

Re: Next.js is infuriating

#463

Post by philipallstar »

> You think I'm joking? There are hundreds of issues with as many emojis with no official response for years. And when you finally get a response, it's to tell you that what you're doing is wrong and a solution to your real problems is on the way. Then they proceed to keep the "solution" in canary for years on end.

It's so much easier to hire people to do prioritisation (or deprioritisation) or code of conduct enforcement or whatever than to just do good work.

Re: Next.js is infuriating

#464

Post by thr0w »

jimbokun wrote: post #278
YuukiRey wrote: post #79

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.

Sounds like Javascript's answer to Spring.

That would be Nest, not Next. A true abomination.

Re: Next.js is infuriating

#466

Post by johnnypangs »

hungryhobbit wrote: post #361
motorest wrote: post #351

Earlier quoted context omitted.

> 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

You have to remember, Next is the only framework that can support some of the features in the latest version of React. To many people, it's just basic logic: "everyone must want the latest React features, and the only way to get those is with Next, so everyone must want Next".

Vite is coming along with rsc at least. https://github.com/vitejs/vite-plugin-react/tree/main/packag...

Re: Next.js is infuriating

#467

Post by dizlexic »

sarreph wrote: post #51

I convinced myself to hate App Router before even trying it because of all the negative sentiment on HN. After using it in three production-scale projects now, I think it's a great isomorphic JS / TS framework. It's as close to a "batteries included" (such as Rails or Phoenix) system that the JS ecosystem has. And yet, people generally like to shit on Next.js I sense because they haven't taken the small amount of tim…

> Was Express ever _that_ easy before you actually understood it and knew what you were doing?

yes

also sails.js was the bomb.

Re: Next.js is infuriating

#468

Post by soiltype »

Demiurge wrote: post #337

Maybe this is a good place to ask... but I was actually considering Next.js as a replacement for Gatsby.js project that is a few years old, but is growing at a steady pace. Given all the negative sentiments, what are better alternatives? I don't even use any SSR, or GraphQL capabilities. The main thing I liked about gatsby vs previous "bring your oown library(router)" are: very little configuring, nice dev server, ea…

I've rebuilt multiple gatsby projects in NextJS recently, and mostly it's actually been pretty nice. However, the crazy high level of abstraction and black-boxing does mean occasionally we run into bugs caused by undocumented behavior and have no idea what is the right way to handle them.

Re: Next.js is infuriating

#470

Post by moritzwarhier »

timcobb wrote: post #301
867567838694 wrote: post #165

Next.js is a cancer. I wish more people would see it sooner before Vercel completely destroys ReactJS.

I thought NodeJS itself was the cancer*. Hard to keep up with all the cancers I guess ;) * https://news.ycombinator.com/item?id=3062271

It's not listed under N

https://web.archive.org/web/20190612110518/http://kill-or-cu...

Post reply on HN