Browsers are pretty good at loading pages

Post by m-p-3 » Sun, Jul 21, 2019, 10:14 PM UTC

guggle wrote: post #99

tiborsaas wrote: post #49

Earlier quoted context omitted.

Because it's faster. If you don't have to download all the content again, force the browser to re-render everything, then by design you just get the new content from the server faster, if you have to download anything at all. The idea exists since the introduction of AJAX. Furthermore, you don't lose state, which makes things much more simple. Imagine a simple image gallery. You just update the tag, update the URL wi…

> Furthermore, you don't lose state, which makes things much more simple. Or not... I think about infinite scrolls with no proper paging.

Post by blattimwind » Sun, Jul 21, 2019, 10:17 PM UTC

tiborsaas wrote: post #49

jakobegger wrote: post #3

I don't get client side navigation. It's a worse experience in every way. It's slow, often doesn't support things like command-click, it usually breaks the back button, and even if it doesn't it breaks the restoration of the scroll position. The only thing worse is a custom scroll UI. Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at…

Because it's faster. If you don't have to download all the content again, force the browser to re-render everything, then by design you just get the new content from the server faster, if you have to download anything at all. The idea exists since the introduction of AJAX. Furthermore, you don't lose state, which makes things much more simple. Imagine a simple image gallery. You just update the tag, update the URL wi…

Post by gruez » Sun, Jul 21, 2019, 10:18 PM UTC

everydaypanos wrote: post #103

He lost me when he described Canada using a dictionary-like wording but also adding some pretty personal perspective. Describing an entire country as Socialist seems super opinionated to me. Client-side navigation is quite tricky to get right - since there is no definition of right. Browser back buttons and scroll positions between back and fourth page loads are not standards-based things and the only way to study th…

Post by lucb1e » Sun, Jul 21, 2019, 10:22 PM UTC

visarga wrote: post #134

jakobegger wrote: post #3

I don't get client side navigation. It's a worse experience in every way. It's slow, often doesn't support things like command-click, it usually breaks the back button, and even if it doesn't it breaks the restoration of the scroll position. The only thing worse is a custom scroll UI. Why do people try to reinvent the most basic features of a webbrowser? And if they do, why do they always only do a half-assed job at…

It's justified if you run a web app that needs to maintain complex state between clicks, such as a text/graphical editor.

Post by lucb1e » Sun, Jul 21, 2019, 10:25 PM UTC

SilasX wrote: post #132

> Most web browsers also store the pages you previously visited so you can quickly go back to them. Not anymore, they don’t. Most of the time I get a huge lag when I hit the back button as all kinds of stuff reloads. I’d prefer if the back button worked like going to a previous tab, where nothing has to reload, but they don’t work like that.