---
title: "Comment by Tarun Sharma on \"Next.js Explained: Why It Became the Default React Framework\" | Hashnode"
description: "Good overview. One thing that's shifted since a lot of these explainers were written: Next 15 flipped fetch and GET route handlers to uncached by default, so th"
url: "https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a95318ef14ac52b5691fdee/comment/6a958b9919e4393159a90486"
---

[Discussion](https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a95318ef14ac52b5691fdee)

Comment [Next.js Explained: Why It Became the Default React Framework](https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a95318ef14ac52b5691fdee)

[Tarun Sharma](https://hashnode.com/@101beardo)

[Aug 31](https://hashnode.com/posts/next-js-explained-why-it-became-the-default-react-framework/6a95318ef14ac52b5691fdee/comment/6a958b9919e4393159a90486)

Good overview. One thing that's shifted since a lot of these explainers were written: Next 15 flipped fetch and GET route handlers to uncached by default, so the automatic caching selling point now needs an explicit opt-in with cache options or the use cache directive. Also worth caveating the ISR description, the very first request after a deploy or a cache eviction still pays a full server render, the CDN only has something stale to serve once at least one request has populated it.
