Live data from Hacker News

Why I'm using Next.js

leerob.io

11–20 of 86 posts

Re: Why I'm using Next.js

#11
There’s a two simple reasons I would go for Next.js

- It’s React-based: Almost everyone knows how to do React these days

- It allows me to build and serve chunked static files, instead of just a single static files like classic SPA

The last part is the main reason for that over other React-based frameworks. While SSR is hot these days, I’m firmly in the camp of “less servers I need to operate is better” and almost have “needs to be servable via S3+CloudFront” as a hard requirement for Frontend stacks.

Re: Why I'm using Next.js

#15
We've been having a lot of problems with weird bugs with nextjs, so I can't really recommend it. Feels like it's a eternal beta.

First, we've had a problem with nextjs not caching the response code for 404 pages, so 404 pages would have a 200 status code. Now they've fixed this they have a bug where they are caching the 304 response code, responding with 304 to every request and completely breaking the site. This has been open for a month now and has affected a lot of people but it seems like Vercel just doesn't care.

https://github.com/vercel/next.js/issues/56018

Re: Why I'm using Next.js

#17
post #6

I never need to write separate backends for projects I want to create. I can build my entire project with Next.js. How have all these other developers been managing this whole time without Next?

They were working as part of a team? Or they are simply too young.

Re: Why I'm using Next.js

#18
post #8

> Because I work at vercel, and because we can monetize frontend with this server-side thing.

But you don't need to use Vercel?

Next’s support outside of Vercel is best effort it seems. Which is fine as Vercel funds it, but it feels like there is a conflict of interest. There is after all a reason for OpenNext’s existence.

Re: Why I'm using Next.js

#19

We've been having a lot of problems with weird bugs with nextjs, so I can't really recommend it. Feels like it's a eternal beta. First, we've had a problem with nextjs not caching the response code for 404 pages, so 404 pages would have a 200 status code. Now they've fixed this they have a bug where they are caching the 304 response code, responding with 304 to every request and completely breaking the site. This has…

This is my big problem with proprietary software; and why open source pragmatically makes more sense.

Fixing bugs is down to priority and incentives of the parent company.

Re: Why I'm using Next.js

#20
post #8

Earlier quoted context omitted.

But you don't need to use Vercel?

Next’s support outside of Vercel is best effort it seems. Which is fine as Vercel funds it, but it feels like there is a conflict of interest. There is after all a reason for OpenNext’s existence.

I definitely agree there can be a conflict of interest, but I also think it's very possible to self host.
Post reply on HN