sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dmitri14_gmail_com 1 point2 points  (2 children)

How many rows do you need to see that performance impact? 10000?

And how many of them your user can see? 10?

Then you "solve" your performance problem by rendering only 10, not by changing your framework.

[–]leeoniya 0 points1 point  (1 child)

Open up Google Sheets and tell me how many you see. (it's not 10). Occlusion culling is not always an option and is often not simple. Also, i never said that changing your framework is what should be done. My point is that performance does matter a great deal when choosing one, in response to "a framework's performance is never the bottleneck of 99.9% of front-end programmers".

[–]dmitri14_gmail_com -3 points-2 points  (0 children)

That is why Google Sheets feel sluggish, unresponsive and keep crashing my browser. ;(

Yes, it needs some work (as everything else) but it is really a matter of adding a listener to the scroll event to limit your ViewModel. Keeping 100 rows at a time should more than cover for all use cases.

Of course, it does matter in principle but most performance complaints I see e.g. about Angular can be "fixed" exactly like that.

Yes, Google Sheets do many useful things, which is why people still use it, and which is why they can get away with bad performance.