|
|
|
|
|
|
by adoxyz
1320 days ago
|
|
|
Caching is a universally difficult problem to solve, but point taken. The majority of my NextJS sites have been deployed to Vercel, but a few have also been hosted on AWS and DigitalOcean. When it comes to incremental regeneration, I didn't use it if the page needed to be 100% up to date for every user, even when on Vercel. As for the forking it comment, that's exactly the point. Vercel is investing heavily into NextJS, spending millions of dollars on hiring full time developers to work solely on it, and they give NextJS away for free. So having the best Next experience on the platform that they own and control and can fine tune makes sense to me. Nobody is forcing you to use NextJS or any other library. |
|
|