When viewing the demo, users don't have much a point of reference for how well their browser performs when scrolling through large amount of data without the component. So when they see the demo, the fact that it is so performant doesn't resonate with them, making the component seem less necessary or less helpful than it actually is.
Suggested solution
I feel it would be useful to add an additional route to the demo app which renders the same data but without the vue-virtual-scroll component. This would make it easier to understand why the component is helpful.
Alternative
Alternatively, for the existing demos, perhaps users could check or uncheck a box to control whether the data is displayed on its own or using the vue-virtual-scroll demo.
Additional context
I cloned the repository and added another route to display the data myself so I could compare the performance. The difference was noticeable -- it was very clear how much more performant the vue-virtual-scroller version was compared to the default browser functionality -- but it would have been more helpful to be able to make that comparison without needing to clone and add the feature myself.
I wouldn't mind creating a PR to add the feature if desired. I haven't done it because I see several open PRs already, some of which are multiple years old.
Clear and concise description of the problem
When viewing the demo, users don't have much a point of reference for how well their browser performs when scrolling through large amount of data without the component. So when they see the demo, the fact that it is so performant doesn't resonate with them, making the component seem less necessary or less helpful than it actually is.
Suggested solution
I feel it would be useful to add an additional route to the demo app which renders the same data but without the
vue-virtual-scrollcomponent. This would make it easier to understand why the component is helpful.Alternative
Alternatively, for the existing demos, perhaps users could check or uncheck a box to control whether the data is displayed on its own or using the
vue-virtual-scrolldemo.Additional context
I cloned the repository and added another route to display the data myself so I could compare the performance. The difference was noticeable -- it was very clear how much more performant the
vue-virtual-scrollerversion was compared to the default browser functionality -- but it would have been more helpful to be able to make that comparison without needing to clone and add the feature myself.I wouldn't mind creating a PR to add the feature if desired. I haven't done it because I see several open PRs already, some of which are multiple years old.
Validations