3 ms·

Yeah, this is shocking to me. I’m a backend developer who occasionally tinkers with frontend. I gave nextjs a spin and couldn’t believe the reload times on a ne

Yeah, this is shocking to me. I’m a backend developer who occasionally tinkers with frontend. I gave nextjs a spin and couldn’t believe the reload times on a new project. For folks who use this every day, how/why is this acceptable?

wirybeige 2y ago
It's acceptable for me because I (and others on my team) do not have to way 6-7 seconds almost ever, it is nearly instant. On odd occasion changes can take a long time to show up, ~5 seconds, but it seems restarting the server fixes it, so not sure what that is about.
- akvadrako 2y ago
  Do you use it on vercel, maybe? I had the same experience of slow refreshes on the NextJS project I worked on (running locally) and the other seasoned NextJS developers didn't think it was unusual.
  - wirybeige 2y ago
    We do not use vercel. Unfortunate that the experience varies so much.
9rx 2y ago
> For folks who use this every day, how/why is this acceptable? While I thankfully don't have to use Nextjs often, in general I am not sure I even launch my app in the browser every single day. Your tests and whatnot are already providing continuous feedback about the state of the code. 6-7 seconds every once in a while wouldn't be the end of the world. But even it were instantaneous, Nextjs has a horrible developer experience for a multitude of other reasons.