[bgwhn]

Thank you for sharing your experience with Next.js, even though you eventually ended up moving off.

> Waiting on Turbopack: Our initial local route loads took 10 to 12 seconds under the full weight of the App Router and RSCs.

Out of curiosity, were you on Next 16.0 or 16.1? We shipped file system caching in 16.1 that greatly improves the initial route loads. https://nextjs.org/blog/next-16-1#turbopack-file-system-cach...

> Production memory leaks

If anyone else runs into this, we've got a guide on how to profile your application: https://nextjs.org/docs/app/guides/memory-usage

> The multi-cloud ceiling

Admittedly hosting Next.js can be a bit harder than a SPA if you're using all the features of the framework, but if you're scaling and you don't want to use Vercel, you've got a lot of other options, including those provided by OpenNext. We've got a nice example repository here: https://github.com/leerob/next-self-host