[docs] Mention Virtuoso as a possible virtualization integration

[petyosi]

Adds a simplified endless scrolling example to the list documentation page, using React Virtuoso.

For a live (more complex) example and step-by-step explanations, check this blog post.

• I have followed (at least) the PR section of the contributing guide.

Thanks for your hard work!

[mui-pr-bot]

No bundle size changes comparing 831c6cc...8ba4ca8

Generated by 🚫 dangerJS against 8ba4ca8

[oliviertassinari]

@petyosi Thanks for sharing, I wish we talked about it before as it's not obvious to me that we should accept the change. Our users value the fact that we make educated decisions for them regarding what the go-to solution for their problem is. Proposing too many options creates friction: What the best option for my use case? Will I miss out if I go with the wrong option? That's the paradox of choice.

So here is my question, why should we document react-virtuoso? We already document react-window and react-virtualized.

[petyosi]

These are valid concerns. Of course, you are not obliged to accept this pull request. react-window is very popular solution.

My motivation for the Virtuoso project is to make a virtualization engine that's easy to use, figures out as much as possible for you and does not require a bunch of manual component assembly for common use cases. Good examples for that are automatic item height, native keyboard navigation, and endless scrolling - all of those come out of the box or super easy to configure.

This PR documents scenario which I consider interesting (without being overly complex) while being a common use case when dealing with Lists. It complements the existing react-window one. Can it increase ambiguity or confuse users? I hope not.

I would love to get some suggestions on how this can be helpful to the Material-UI community. Thank you for your time!

[stunaz]

When it comes to integration with third-parties, I don't think that Material-UI should be that opinionated. the choice should be left to end-users. Out-of-the-box solution from material-ui/core/lab/styles ..., should be opinionated, they shouldn't be friction there.

So maybe, the list Demo is not the right place to put it, maybe in an integrated demo section or something...

just my 2 cents...

[oliviertassinari]

I would be fine with the following: we link react virtualized at the end of the react-window demo, explaning that it's better suites for advanced use cases. We link virtuoso as a possible alternative, we don't add any live demo.

What do you think?

[petyosi]

@oliviertassinari Thanks for the consideration! I have removed the live demo and the section header. Let me know if this is what you had in mind.

[oliviertassinari]

I have rephrased the content a bit to emphasize the order people should try the different modules.

updated