Another example that particularly riles me is that NextJS forces the "edge runtime" (from Vercel) on middleware even when your server is otherwise running in no

Another example that particularly riles me is that NextJS forces the "edge runtime" (from Vercel) on middleware even when your server is otherwise running in nodejs. The implication is that you can't do anything that relies on node APIs that edge doesn't support which can be quite limiting. There's rumour that they're walking back this decision, but it always struck me as an arbitrary way to "encourage" codebases to make themselves compatible with edge which in turn would make deploying using Vercel easier. (In general I'm reasonably happy using NextJS, though there are many architectural decisions that I find frustrating)