The post discusses significant concerns and frustrations with Next.js, particularly its transition from the pages router to the app router, which some developers find detrimental to their workflow. Key complaints include long development build times (6-7 seconds for changes), a feeling of being locked into Vercel's hosting environment, and complexity for developers who are new to deployment and system management. Despite these criticisms, some argue that Next.js offers advantages like server-side rendering (SSR) for React developers without requiring additional learning. Alternatives are being explored by developers creating independent frameworks that aim to improve on these issues. Overall, there's a growing discourse around the future of Next.js amid the challenges posed by Vercel's influence and developer frustrations.