> That's where ~all of Next.js' complexity comes from Complexity does arise there, but equally arises from limitations imposed by the Vercel service that Next.

> That's where ~all of Next.js' complexity comes from Complexity does arise there, but equally arises from limitations imposed by the Vercel service that Next.js ultimately needs to deal with. A lot of its seemingly dumb design decisions make sense once you consider the constraints Vercel (the service) forces upon it, but they are still poor decisions you have to live with that wouldn't have been necessary if it were intended to run in a "normal" computing environment.