groundzeros2015 2 hours ago

This is how every scrolling list has been implemented since the 80s. We actually lost knowledge about how to build UI in the move to web

▲

bloomca an hour ago | parent [-]

The biggest issue is that there is no native component support for that. So everyone implements their own and it is both brittle and introduces some issues like:

- "ctrl + f" search stops working as expected - the scrollbar has wrong dimensions - sometimes the content might jump (common web issue overall)

The reason why we lost it is because web supports wildly different types of layouts, so it is really hard to optimize the same way it is possible in native apps (they are much less flexible overall).

	▲	TeMPOraL 20 minutes ago \| parent [-]
		Right. This is one of my favorite examples of how badly bloated the web is, and how full of stupid decisions. Virtual scrolling means you're maintaining a window into content, not actually showing full content. Web browsers are perfectly fine showing tens of thousands of lines of text, or rows in a table, so if you need virtual scrolling for less, something already went badly wrong, and the product is likely to be a toy, not a tool (working definition: can it handle realistic amount of data people would use for productive work - i.e. 10k rows, not 10 rows).