3 ms·
> it fills the page (and therefore memory) with lots and lots of entries Yet observables are all the rage. Additionally, can't you just move prior entries out,
by bdcravens 10y ago
> it fills the page (and therefore memory) with lots and lots of entries
Yet observables are all the rage. Additionally, can't you just move prior entries out, so the "scroll and fetch" goes both ways?
> disallows me to quickly navigate to exact place in the view I need
I've seen infinite scrolling that implements paging as well
In general I'll agree infinite scrolling isn't implemented well, and is usually just the result of dropping in a module and forgetting about UX.
- jack9 10y ago> I've seen infinite scrolling that implements paging as well Then you're using offsets, which is the crux of the disagreement regarding the utility of offsets.
- ak4g 10y agoI'm sure he means infscroll using keyset pagination. The UX, as noted, is ugly - have to somehow support scrolling in both directions with some sort of lazy-loading - but pagination in this context doesn't === offset-based pagination.