4 ms·
I disagree with that. There's no real reason for each page to be a separate SPA, most likely only a small part of that page will be interactive, and most of it
by dlisboa 5y ago
I disagree with that. There's no real reason for each page to be a separate SPA, most likely only a small part of that page will be interactive, and most of it will be cacheable. Extracting only the interactive parts of a page into components is what I'm talking about. In some cases that'll be all of the page, but there are very few apps that meet that criteria.
- prmph 5y agoOf course if only a small part of your app is interactive, then SPAs don’t come into the picture in the first place. My point is that for very interactive web apps, this is a significantly better architecture that a huge monolithic SPA
- LAC-Tech 5y agoI mean in this model, if each page is an SPA, then the line between an SPA and an interactive page is very blurry.
- tracker1 5y agoNot only that but bundle splitting allows for extra areas of the application to be loaded at runtime on demand. All of that said, I'm not opposed to approaches like Next/Nuxt/Aleph.