Live data from Hacker News

Why I'm using Next.js

leerob.io

1–10 of 86 posts

Re: Why I'm using Next.js

#4
I use it, because SaaS vendors like Sitecore and many others, have agreements with Vercel to push it as the main SDK.

While other SPA frameworks are supported, they are a kind of second line, without all the bells and whistles that Next.js users are given to enjoy.

Re: Why I'm using Next.js

#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?

Re: Why I'm using Next.js

#7
My experience with NextJS has been very frustrating.

- it adds a layer of opacity between the front and backends (or as they are in Next: the frontend, the frontend backend and the backend backend).

- front end code can run in the frontend backend and consequently needs a lot of extra guards.

- front end stack traces are almost completely useless in dev mode. If you’re lucky, they will include the file name where the issue occurred, but often in these cases the line number will point to an empty line.

I think the common thread here is that Next has a lot of surprises, especially when not on the happy path. It frequently breaks my intuition about how the web works. I’m strongly considering migrating our Next projects to React.

Post reply on HN