3 ms·
Note that Nue will probably work just fine for your use case. The list is not re-rendered when individual items on the list are updated or when new items are ad
by tipiirai 3y ago
Note that Nue will probably work just fine for your use case. The list is not re-rendered when individual items on the list are updated or when new items are added. Currently only re-rendered when the whole list is sorted or replaced with a new one. Based on the feedback here looks like I need to optimize these two mass-operations as well.
- latchkey 3y agoI don't want to manage the list on the client side. I just do a replacement of the data retrieved from the server, and it all magically works because the ID's don't change.
- tipiirai 3y agoIndeed. It's rare to see real-world scenarios where thousands of items are mass-manipulated on the client side. They exist, but rarely. The lists are typically appended/prepended or individual items are updated.
- Timon3 3y ago> Indeed. It's rare to see real-world scenarios where thousands of items are mass-manipulated on the client side. They exist, but rarely. I'm not sure this is correct. Almost all apps that I write that display live data are built by replacing the whole client-side array with updated server-side array data, and the other commenters seems to work similarly. With your current approach I'd have to write a complete diffing logic to modify the array in-place locally, especially if I don't want child components to be re-mounted.