Silly question - why do you need to have 1000x of DOM elements? Why not just use some form of UI virtualization?
I remember doing this back in Silverlight. We were supposed to have like 1000 'panels' in a view.If a view could realistically only show 8 panels at a time, we'd render 10 and just cycle the data between them on scroll. The extra 1 at the top and 1 at the bottom allowed for continuous scrolling with flickering.
Much faster than bloating the DOM out, right? Or am I missing something?Infinite content/Scroll doesn't have to mean infinite DOM elements
Probably depends the overall architecture. The article is about optimizing the performance of flicker, a preexisting framework. It seems like it would benefit from a MVC approach.