Next.js is infuriating (News)

September 2, 2025

8 min episode · 2 min read

Jim Mesnick,Christian Roca

Episode

8 min

Read time

2 min

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓Next.js extensibility: Framework's rigid architecture and limited middleware options create daily friction for developers, with issue tracker containing numerous unresolved complaints about abstraction layers and Vercel-driven roadmap priorities.
✓Open source maintenance reality: Analysis of 11.8 million projects shows 7 million have single maintainers; among packages with 1+ million monthly downloads, nearly 50% are maintained by one person alone.
✓License protection strategy: Bear adopts Elastic license after MIT allowed competitors to fork and deploy with minimal modification, joining six other projects preventing hosted service clones while maintaining open code access.

What It Covers

Developer frustration with Next.js framework limitations, open source sustainability challenges with solo maintainers, and Bear blogging platform switches from MIT to Elastic license.

Key Questions Answered

•Next.js extensibility: Framework's rigid architecture and limited middleware options create daily friction for developers, with issue tracker containing numerous unresolved complaints about abstraction layers and Vercel-driven roadmap priorities.
•Open source maintenance reality: Analysis of 11.8 million projects shows 7 million have single maintainers; among packages with 1+ million monthly downloads, nearly 50% are maintained by one person alone.
•License protection strategy: Bear adopts Elastic license after MIT allowed competitors to fork and deploy with minimal modification, joining six other projects preventing hosted service clones while maintaining open code access.

Notable Moment

Herman Martinis describes the pain of watching years of work on Bear get forked into competing services within hours, threatening his livelihood despite believing in open source principles.

Know someone who'd find this useful?