5 ms·
> The key advantage to an SPA is fewer full page loads - you only load resources as you need them, and you don't re-load the same resources over and over. I do
by Quanttek 11y ago
> The key advantage to an SPA is fewer full page loads - you only load resources as you need them, and you don't re-load the same resources over and over.
I don't know much about web development, but shouldn't those resources get cached? Isn't the disadvantage of SPAs that you are unable to link to / share a specific piece of content?
- baby 11y ago> but shouldn't those resources get cached? server side yes, what he means is that you only need to load the content as a client now, not the layout. > Isn't the disadvantage of SPAs that you are unable to link to / share a specific piece of content? If it's well done no, since you can dynamically update the URL with javascript.
- blowski 11y ago> Isn't the disadvantage of SPAs that you are unable to link to / share a specific piece of content? Actually, this is achievable with push states, so isn't a strong argument against single page apps. I think the problem with SPAs is that they exacerbate memory leaks, since they don't have the typical 'reset' of a browser page load to clear them. Also, a lot of SPAs re-implement browser functionality like scrollbars and the back button without proper cross-browser testing - let alone usability testing. Conceptually, there's nothing wrong with SPAs, but many of the implementations are shoddy at best with no clear advantage gained.