Next.js
9 statements across 2 episodes · 3 bullish · 1 bearish · 2 people on the record · first statement Nov 2, 2023 by Guillermo Rauch · said 33 times in 3 episodes since 2023 · across every show →
Mentions by year
brought up most by Guillermo Rauch (24), Todd Jackson (6), Jeanne DeWitt Grosser (2), Paul Copplestone (1)
tap a year for its mentions
2026 3 mentions in 2 episodes 2 per episode
Everything said about Next.js, oldest first
Nov 2, 2023
Nov 2, 2023 positive
Nov 2, 2023 neutral
Nov 2, 2023 negative
Developer experience at all costs is counterproductive for businesses and developers
“The framework that I use today is developer experience at all costs doesn't work. It it's bad for the vendor startup enterprise. It's bad for the developer because the end date is like the good old adage of the customer is king. We all get paid. You, me, like …”
Nov 2, 2023
Redfin and Trulia independently built Next.js lookalikes before its launch
“So I remember right, right after we released it, someone from Redfin reached out and they were saying, we're building the same thing. And then a week later, someone from Trulia reached out, oh, we're building the same thing.”
Nov 2, 2023 positive
A 2014 essay on rich web applications became the blueprint for Next.js
“In 2014, I had written this article and I highly recommend this to prospective founders. I wrote this essay called The Seven Principles of Rich Web Applications. It's the first essay on my blog. I think this was right, right after I had sold the company. And t…”
Nov 2, 2023 positive
Pure developer experience frameworks failed because user performance never solved itself
“There was a lot of optimism that certain things that were really good developer experiences, For whatever magical reason, let's call it Moore's law or just hopium. They were like, okay, the user part will figure itself out. You know, fast forward a few years, …”
Nov 2, 2023
Highly regulated customers use Vercel exclusively for pre-production workflows
“We have, for example, customers in extremely highly regulated hosting environments that cannot even use cloud. So they use Vercel as a way of speeding up the iteration cycle of their Next.js project. So they use it exclusively pre-production.”