Next.js is infuriating (News)
Episode
8 min
Read time
2 min
Topics
Software Development, Product & Tech Trends
AI-Generated Summary
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.
Episode Transcript
What's up, nerds? Shaboy. I'm Jared, and this is change log news for the week of Monday, 09/01/2025, but recorded on Tuesday because Labor Day. If you need an uplifting story that displays the human spirit triumphing over tyranny, look no further than your local Taco Bell drive thru. My favorite fast food chain has been forced to rethink their AI ordering system after one heroic patron crashed it by ordering 18,000 waters. Now that's what I call high quality h two o. Okay. Let's get in to this week's news. Next j s is infuriating. Dominic Mecha finally decided to write a blog post because anger is the best motivator, and he's angry at Next JS. Quote, the Next JS devs have a vision, and it's either their way or the highway. Note that if it was just the middleware, I wouldn't be sitting here wasting away my weekend ranting about a React framework. Believe it or not, I've got better things to do. It's constant pain you encounter daily when working with Next. Js, end quote. After ranting some more, Dominic points to the issue tracker and calls it a dumpster fire, which I looked at it too, and I have a hard time to screen with him. Hacker news commenters had a field day with this post. The top comments, there were over 400 as I read this, vehemently agree with him. I'd summarize the core complaint as too many layers of abstraction with a sprinkle of not enough extensibility and a dash of Vercel based feature road map. Open source is one person. Josh Bressers was offended by the register's recent story titled Putin on the code. DOD reportedly relies on utility by a Russian dev. Quote, if you're not real smart, it seems like pointing out that an open source project is written by one person in a country you don't like is a bad thing. It could be, but it also could be that the software running the whole effing planet is written by one person in a country. We have no idea which country. It's not the same person, mind you, but it is one person, end quote. Josh goes on to point out with receipts that almost all open source is literally one person. Quote, a project exists called ecosystems that catalogs a lot of open source. Most of it, I would guess, but not all. They currently have 11,800,000 open source projects in their database. So what do we mean by one person is open source? What I mean is, if we look at the projects that ecosystems is tracking, how many have a single person maintaining that project? It's about 7,000,000 projects, end quote. He also looks at NPM package downloads and found that of the projects with over 1,000,000 downloads this month, which is a proxy for usefulness, about 6,000 of them have solo maintainers, while 6,800 of them have more than one maintainer. That's almost half. Why copy …
Get the full transcript (1,316 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 5-minute episode.
Get The Changelog summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from The Changelog
Forking Cal.com to closed source (Interview)
Sep 3 · 114 min
Software Engineering Daily
Open Source Sustainability
May 14
More from The Changelog
Postgres at PlanetScale (Interview)
Aug 25 · 102 min
Moonshots with Peter Diamandis
OpenClaw Explained: Baby AGI, Security Threats, and How a Mac Mini Became Everyone's Supercomputer | #237
Mar 9
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.
Tools
“SPONSORS: Zed (https://zed.dev/blog)”
by Vercel
“Developer frustration with Next.js framework limitations... 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.”
More from The Changelog
We summarize every new episode. Want them in your inbox?
Forking Cal.com to closed source (Interview)
Postgres at PlanetScale (Interview)
Canary tokens and digital tripwires (Interview)
From open source hits to OpenAI (Interview)
MCP on Code Mode (Interview)
Similar Episodes
Related episodes from other podcasts
Software Engineering Daily
May 14
Open Source Sustainability
Moonshots with Peter Diamandis
Mar 9
OpenClaw Explained: Baby AGI, Security Threats, and How a Mac Mini Became Everyone's Supercomputer | #237
Invest Like the Best with Patrick O'Shaughnessy
Sep 1
Sarah Guo - What the 250 People Building AI Believe - [Invest Like the Best, EP.489]
20VC (20 Minute VC)
Aug 29
20VC: Is Anthropic's Coding Business Worth $2 Trillion? | Should American Enterprises Work With Open-Source Chinese Models? | Why 80–90% of Neo-Labs Die in the Next 18 Months? with Eno Reyes, Co-Founder @ Factory
a16z Podcast
Jul 27
Steven Sinofsky: AI Doesn't Need New Rules Yet
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into The Changelog.
Every Monday, we deliver AI summaries of the latest episodes from The Changelog and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime