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

441–450 of 602 posts

Re: Next.js is infuriating

#441

Post by [deleted] »

fourseventy wrote: post #357
throwaway77385 wrote: post #292

Earlier quoted context omitted.

I'm so glad I'm not the only one thinking this. I built a medium-complexity, money-making, production-grade app in Next.js and started out on Vercel's hosting (and Google Firebase) and then moved to hosting myself and stripping out Firebase, replacing it with Pocketbase. Pocketbase was the ONLY good thing about this journey. Everything else sucked just so terribly. Infinite complexity everywhere, breaking changes CON…

" Codebases from years ago are still rock-solid." This is the biggest thing for me. I recently pulled down an 8 year old hobby Java/Maven project I had and it compiled and ran perfectly on the first try. Imagine trying to get an 8 year old javascript project to work...

[deleted]

Re: Next.js is infuriating

#442

Post by Sohcahtoa82 »

christophilus wrote: post #83
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.

Second worst for me. I’ve used Sharepoint.

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.

Re: Next.js is infuriating

#443

Post by jeppester »

tiku wrote: post #33

Through a customer I've come into contact with InertiaJS. React with Laravel made my work so much simpler. Routing through Laravel was easier for me. The data sharing from Laravel to the frontend is painless. I also like the server side, PHP works better for me than a Javascript server. I've had some weird bugs with nodemon, pm2 and other server tools.

I also recommend inertia.

It really doesn't do much, which is very refreshing coming from Nextjs.

It's simple tooling for backend for frontend-style APIs, taking care of basic routing, fetching of data, and submitting forms.

While inertia was invented for Laravel, I'd argue that it works even better with Adonisjs. Because Adonisjs is TypeScript you can infer the types coming from the backend.

Re: Next.js is infuriating

#444

Post by Sohcahtoa82 »

RaptorJ wrote: post #296
amonith wrote: post #218

Earlier quoted context omitted.

eh `cmd /C "set KEY=value && ./myApp"` isn't that bad if you really need complete isolation.

or directly in powershell, `Start-Process myproc.exe -Environment @{ FOO = 'bar' }`

What an absolutely awful syntax.

How Powershell ever got popular is beyond me.

Re: Next.js is infuriating

#445

Post by tshaddox »

digianarchist wrote: post #424
pavel_lishin wrote: post #226

> Let's not skip over the fact that you can't have multiple middlewares or chain them either. Surely this can't be right? https://nextjs.org/docs/messages/nested-middleware > If you have more than one Middleware, you should combine them into a single file and model their execution depending on the incoming request. By Talos, this can't be happening.

I can’t help but feel some of these decisions are made because it’s what is best for Vercel and not what’s best for the framework.

I don't see how this particular case makes anything better or worse for Vercel. It's just a poor developer experience to need to come up with your own composeMiddlewares function (or find one of the many that people have posted in various threads).

Re: Next.js is infuriating

#446

Post by hombre_fatal »

motorest wrote: post #417
hungryhobbit wrote: post #361

Earlier quoted context omitted.

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".

> You have to remember, Next is the only framework that can support some of the features in the latest version of React. That is extremely fishy, isn't it?

Not necessarily since they have to do with the inherently complex niche features like unified server/client rendering (e.g. RSC, streaming SSR with selective hydration, server actions).

Next.js is essentially the reference and test bed impl.

Where people go wrong is thinking they need to default to the inherently complex niche feature of client hydration which is a niche optimization enabled by a quirk of web tech.

Re: Next.js is infuriating

#447

Post by 9rx »

fragmede wrote: post #422
recursive wrote: post #414

Earlier quoted context omitted.

Basic react experience presumably. As a first approximation, it seems like every possible interview sounds like a bad interview to someone. What has worked well for you?

Seems more like a test on random React minutiae. Like, let's take some framework, take away some random piece. How well do you know the area around that random piece we just removed? Frameworks are large and gnarly (or there isn't enough to them). Expecting a candidate to be lucky and know random implementation details in the area that happened to be picked doesn't seem like you'd select for anything other than luck.…

> Seems more like a test on random React minutiae.

It is more like test on whether or not you can figure out random React minutiae (with Google/ChatGPT, if needed) when presented with a need. Which isn't a bad approximation for how well you will do at finding any random minutiae as needs present themselves. React-based development doesn't require much original thought — the vast majority of the job really is just figuring out the minutiae of your dependencies to fit your circumstantial need.

For fun, I asked ChatGPT for an answer and it gave a perfectly good one back without hesitation. Even if you had no idea what React was beyond knowing it is a library for developing web components, you should still be able to answer that particular question with ease.

Re: Next.js is infuriating

#448

Post by koonsolo »

fragmede wrote: post #397
koonsolo wrote: post #316

Earlier quoted context omitted.

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.

Why? Microsoft's GUI framework as well as Apple's covered plenty of use cases before the rise of the web browser.

Then why did HTML became so popular if win32 or MFC were so great?

Re: Next.js is infuriating

#449

Post by fragmede »

9rx wrote: post #447
fragmede wrote: post #422

Earlier quoted context omitted.

Seems more like a test on random React minutiae. Like, let's take some framework, take away some random piece. How well do you know the area around that random piece we just removed? Frameworks are large and gnarly (or there isn't enough to them). Expecting a candidate to be lucky and know random implementation details in the area that happened to be picked doesn't seem like you'd select for anything other than luck.…

> Seems more like a test on random React minutiae. It is more like test on whether or not you can figure out random React minutiae (with Google/ChatGPT, if needed) when presented with a need. Which isn't a bad approximation for how well you will do at finding any random minutiae as needs present themselves. React-based development doesn't require much original thought — the vast majority of the job really is just fig…

I was assuming that particular interview was not open ChatGPT. If all you want to test for is can you understand the words that are coming out of my mouth, type that into ChatGPT, and then read it to me, yeah, it seems fine.

Re: Next.js is infuriating

#450

Post by [deleted] »

fragmede wrote: post #449
9rx wrote: post #447

Earlier quoted context omitted.

> Seems more like a test on random React minutiae. It is more like test on whether or not you can figure out random React minutiae (with Google/ChatGPT, if needed) when presented with a need. Which isn't a bad approximation for how well you will do at finding any random minutiae as needs present themselves. React-based development doesn't require much original thought — the vast majority of the job really is just fig…

I was assuming that particular interview was not open ChatGPT. If all you want to test for is can you understand the words that are coming out of my mouth, type that into ChatGPT, and then read it to me, yeah, it seems fine.

[deleted]
Post reply on HN