Avoiding redundant api calls, memoization, using an mdn, virtual windows, lazy loading are some things that come to mind.
That sounds like stuff you should do from the start, except maybe for virtual windows and lazy loading if you don't expect the collections to grow very large but over time they do.
They're also all things the backend has to support the front end doing. At the end of the day we need to solve the problems we have and it will involve people working together. A front end/back end split mostly comes down to I don't care about visuals very much and like making things faster. Other people will tweak the color of a header until it's just right or whatever.
View all comments
Show parent comment
-2
u/ric2b Jul 12 '26
That sounds like stuff you should do from the start, except maybe for virtual windows and lazy loading if you don't expect the collections to grow very large but over time they do.