users don’t really like when every action requires a page refresh/loading a new page, and unfortunately the only way to avoid that is with a shitty JS based SPA
Virgin Web App: uses full SPA to reduce page refreshing, website shows hours of full page "skeleton loaders" and spinners.
Chad Website: just makes website fast instead, ignores trendy things like javascript.
For a real example, one of my friend's college math assignments were on a website that reloaded the page for every answer submission. Which in terms of not using JS makes sense, the only way to submit something is through a new request and the only way to make a request that doesn't reload the page is through JS.
But it was still jarring. By definition everything has to disappear from your screen then be redrawn. And no matter how fast your site is, how fast your servers are, how tiny your response is, the browser itself takes enough time refreshing the page that people will notice. No one likes that.
Add on the fact that you can lose your scroll position (don't you just love it when a site snaps back to the top?) and it gets even worse. There's not even much a well designed site could do about that.
And really I'm saying all this because it sucks that there's no good option, for both the end user and the developer.
Virgin Web App: uses full SPA to reduce page refreshing, website shows hours of full page "skeleton loaders" and spinners.
Chad Website: just makes website fast instead, ignores trendy things like javascript.
It doesn't matter how fast the website loads, the browser still makes it clear that the page is reloading, and people don't like it.
Virgin Web App: thinks people care about page reloading, also you have to reload anyways all the time because of bugs
Chad Website: knows the only thing users don't like about page reloading is how slow it is, makes a fast website
For a real example, one of my friend's college math assignments were on a website that reloaded the page for every answer submission. Which in terms of not using JS makes sense, the only way to submit something is through a new request and the only way to make a request that doesn't reload the page is through JS.
But it was still jarring. By definition everything has to disappear from your screen then be redrawn. And no matter how fast your site is, how fast your servers are, how tiny your response is, the browser itself takes enough time refreshing the page that people will notice. No one likes that.
Add on the fact that you can lose your scroll position (don't you just love it when a site snaps back to the top?) and it gets even worse. There's not even much a well designed site could do about that.
And really I'm saying all this because it sucks that there's no good option, for both the end user and the developer.
deleted by creator