Native CSS transitions have quietly killed the strongest argument for client-side routing. Yet people keep building terrible apps instead of performant websites.
in your case the user list would be rendered by the server and the client wouldn’t care, it would receive a new rendered copy when you changed pages.
it seems like their argument was all just sites that should have been fully static to begin with, and for some reason have made it sound like that’s the main use of SPAs. It’s a silly article and I wouldn’t change anything I’m doing based on it. if your site is a content based site(showing docs/articles/etc.) then you shouldn’t be using an SPA, especially just for page transitions. otherwise you have a valid use for an SPA and should continue regardless of these new APIs
in your case the user list would be rendered by the server and the client wouldn’t care, it would receive a new rendered copy when you changed pages.
it seems like their argument was all just sites that should have been fully static to begin with, and for some reason have made it sound like that’s the main use of SPAs. It’s a silly article and I wouldn’t change anything I’m doing based on it. if your site is a content based site(showing docs/articles/etc.) then you shouldn’t be using an SPA, especially just for page transitions. otherwise you have a valid use for an SPA and should continue regardless of these new APIs