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

261–270 of 602 posts

Re: Next.js is infuriating

#261

Post by DanielHB »

panny wrote: post #213
DanielHB wrote: post #27

When I first saw Next.js I was immediatelly reminded of Meteor.js. I did invest a bit in learning into it and did some personal projects. But quickly realized it was both over-abstracted and inflexible which made it really hard to get it past prototypes. But these solutions keep coming up because they bring one thing: Self-contained / "batteries included". Just the other day there was a thread in hackernews about Lar…

>both over-abstracted and inflexible which made it really hard This seems to be built into the culture of companies which have those ridiculous whiteboard leetcode interviews. You find people who can produce very clever complex solutions in their sleeep, and then they do that. Interviews aren't selecting for people whose strength is simplicity and clarity instead. So you get a lot of tight loop optimizers and they ti…

Yeah, clever code is the bane of my existence.

Only my own code is allowed to be clever!

Re: Next.js is infuriating

#262

Post by felipeccastro »

motorest wrote: post #192
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.

> 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…

The train of thought is “what is everyone using? I’ll use that too”

Re: Next.js is infuriating

#263

Post by dncornholio »

Just run production with the right flags so it'll log? Or put the app into local and try to replicate? The tone of voice is also completely off.

It seems Middleware in Next.js is not what Middleware is in framework X. This whole thread looks like a complete collection of misunderstandings of Next.js.

Re: Next.js is infuriating

#264

Post by iw7tdb2kqo9 »

kremi wrote: post #190

I think “middleware” is a bit of a misnomer in Next.js. It’s really an edge function that runs before your request hits the app -- quick header checks, routing, and other lightweight guards. It runs on the edge runtime, not on the app server. The post's author seems to conflate the edge runtime with the server runtime. They’re separate environments with different constraints and trade-offs. I struggled with Next.js a…

Finally someone with a brain.

If learn what is a package/module in python, try to apply that in Go without any brain power, you will complain that Go is bad. If you are using any technology, you should have some knowledge about that technology.

Re: Next.js is infuriating

#265

Post by wateralien »

I've just convinced a large, but not global, client to move from their antiquated system to Next.js. They definitely wouldn't want to run on Vercel in prod since they're obsessed with costs.... and now I'm really concerned since this and some other "next.js in production nightmares" posts have dropped. I've only ever run smaller stuff on Vercel. Super concerned.

Re: Next.js is infuriating

#266

Post by iw7tdb2kqo9 »

yladiz wrote: post #234
kremi wrote: post #190

I think “middleware” is a bit of a misnomer in Next.js. It’s really an edge function that runs before your request hits the app -- quick header checks, routing, and other lightweight guards. It runs on the edge runtime, not on the app server. The post's author seems to conflate the edge runtime with the server runtime. They’re separate environments with different constraints and trade-offs. I struggled with Next.js a…

> But blaming Next.js for that complexity is like blaming a toolbox for having more than a hammer. The biggest issue is that the complexity is self-inflicted. The term middleware has a pretty well understood meaning if you've worked with basically any other framework in any language: it's a function or list of functions that are called at runtime before the request handler, and it is assumed those functions run in th…

As I have mention in another comment

> If learn what is a package/module in python, try to apply that in Go without any brain power, you will complain that Go is bad. If you are using any technology, you should have some knowledge about that technology.

Re: Next.js is infuriating

#267

Post by Etheryte »

pjmlp wrote: post #49
Etheryte wrote: post #6

Earlier quoted context omitted.

I don't think the post is an unreasonable complaint. The fact that you have to even think about how to get logs out of your application is insane, never mind all the hoops you need here. Logging should be a first class citizen in anything that goes to production.

Interesting, because that is hardly so in most frameworks, logging requires additional libraries and configuration almost everywhere.

In most languages and frameworks logging is as simple as import, initialize, done. Here it's far from it.

Re: Next.js is infuriating

#268

Post by marcosdumay »

mcny wrote: post #131
christophilus wrote: post #83

Earlier quoted context omitted.

Second worst for me. I’ve used Sharepoint.

Third worst if you have used Lotus Notes mail. I still don't understand how an email and calendar client can slow down a computer like that (going by memory, the last time I used it was at work in 2013 so pre-SSD days).

Well... I don't know exactly what the OP meant by "technology", but Notes at least wasn't supposed to be a development platform.

It surely was a development platform, but wasn't supposed to be one.

Re: Next.js is infuriating

#270

Post by pjmlp »

Etheryte wrote: post #267
pjmlp wrote: post #49

Earlier quoted context omitted.

Interesting, because that is hardly so in most frameworks, logging requires additional libraries and configuration almost everywhere.

In most languages and frameworks logging is as simple as import, initialize, done. Here it's far from it.

Really, which ones?

Because anything Java, .NET and Python, it certainly requires configuration and related infrastructure.

Post reply on HN