Sean J. Miller
It finally jumped out for me. I'm learning Next.JS and they stated the following:
Furthermore, in a production build of Next.js, whenever
Link components appear in the browser’s viewport, Next.js automatically prefetches the code for the linked page in the background. By the time you click the link, the code for the destination page will already be loaded in the background, and the page transition will be near-instant!
Client-Side Navigation - Navigate Between Pages | Learn Next.js (nextjs.org)
For example, let's say I have a DIV that appears collapsed with an icon to expand it. When its expanded, it's going to show a pretty table of the 10 day weather forecast. This could already be fetched by the time they click the icon.
At work, I had dreamed up a Field Guide concept. Everything you ever would dream of is on one single page. However, being written with JQuery, each click, the user has to wait for a spinning GIF while the sections are loaded.
Now sure, I could do some clever setTimeOut routine that runs to get stuff, but that gets messy. With Next.js, every hidden div the user could twist out can be a different "page", allowing you to split the code out for easier readability. I wish they used a different term than page, but I guess you just got to get your head around it. They chose it because you can link just to a blurb of code or use it like it's a routed page on an old school server.