Page refresh doesn't happen fast enough as background interactions and rendering result as it arrives. This implies SOME logic on a client.
This is specifically true for remote sites. You will have at best speed of light delay before retrieving content. In worst case network fluctuations might give very annoying delay just to get new content. Yes, and you customer will be staring at WHITE page, because browser viewport have nothing to render.
This is why I am so assertive.
If you don't like it, fine - learn your way ;)
Modern browsers smart enough to cache your megs once and then transmit pure json back and forth, reducing overall need for bandwidth. Plus it happens behind the scene, so customer might enjoy that spinner animation or enjoy previously loaded content.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why are you asserting that you cannot have a "smooth UX" with this approach. What is not smooth about how it works now?
I'll tell you what isn't smooth, downloading megs of javascript and executing it on a low power device.
Because I was using 90xx web.
Page refresh doesn't happen fast enough as background interactions and rendering result as it arrives. This implies SOME logic on a client.
This is specifically true for remote sites. You will have at best speed of light delay before retrieving content. In worst case network fluctuations might give very annoying delay just to get new content. Yes, and you customer will be staring at WHITE page, because browser viewport have nothing to render.
This is why I am so assertive.
If you don't like it, fine - learn your way ;)
Modern browsers smart enough to cache your megs once and then transmit pure json back and forth, reducing overall need for bandwidth. Plus it happens behind the scene, so customer might enjoy that spinner animation or enjoy previously loaded content.