Earlier quoted context omitted.
> a feature that simply makes your product easier to use Except it doesn't. You lose context and are now drowning in an endless morass of lazy-loaded blocks and widgets, all hiding under invisible elements. Nothing has a permanent URL, so there is zero accountably if the user was shown something that they need to reference - unless it benefits the platform. And of course, it will eventually all force reload when the…
X posts have a permanent url.
[1]: something like a link specifying the contents of my feed at a specific date+time and scroll-position.
…whereas with old-school SSR paging it’s right there in the querystring paging params (page-size, page-index or item-offset, and an optional results anchor for stability).
I’ll concede that a well-designed infinite-scrolling (or “click to load more inline” button) feature could use history.pushState to dynamically update the browser’s address with new query params but I don’t think I’ve ever actually seen anyone do that - which is a shame.