On the other hand, I do believe they drifted too much and stopped listening. As someone else said it - most of the fancy features are used by 1% of the projects, and everything else is buried in hacks and workarounds.
I also agree the tone (and especially the AI brag) is a bit too much. And at the same time it's honest - it doesn't need to be THAT hard and complex. Nor slow :)
That's why I've written an open letter to fix Next.js, to whomever wants to do it (Vercel, Cloudflare or anyone else). Because we have needs, and we cannot play this game anymore...
https://please-fix-next.com/ if you're interested
I just wrote an open letter to fix Next.js. The goal is to compile a list of needs for whoever decides to fix those in any way possible...
The GitHub repo has discussion posts with specific pain points — not venting, actual proposals. Would love to hear what's broken for others.
vinext proved last week that Next.js complexity now becomes a choice, not a necessity. This is an open letter from developers who built Next.js' reputation and want it back. The GitHub repo is where we're compiling the actual pain points.