Why I'm using Next.js
leerob.io
Why I'm using Next.js
1–10 of 86 posts
Re: Why I'm using Next.js
#2Re: Why I'm using Next.js
#3Re: Why I'm using Next.js
#4While 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
#5Re: Why I'm using Next.js
#6How have all these other developers been managing this whole time without Next?
Re: Why I'm using Next.js
#7- 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.
Re: Why I'm using Next.js
#8> Because I work at vercel, and because we can monetize frontend with this server-side thing.
Re: Why I'm using Next.js
#9Because you work there, no need for this blog post. This is more of an ad than anything.
Re: Why I'm using Next.js
#10Because you work there, no need for this blog post. This is more of an ad than anything.