For streams, we currently load all particles for the stream. Should we load a count and current index and then only load the particles that are nearest? Or have pagination so only show a few bars and then one color bar that indicates that there are more pages?
For now, maybe we are fine with loading all, and we won't have any performance issues with our current product? No need to optimize for some outlier case of running out of memory here or reducing costs?
We should assess this holistically, especially how we will need it for more tools like quests and folders of files.
For streams, we currently load all particles for the stream. Should we load a count and current index and then only load the particles that are nearest? Or have pagination so only show a few bars and then one color bar that indicates that there are more pages?
For now, maybe we are fine with loading all, and we won't have any performance issues with our current product? No need to optimize for some outlier case of running out of memory here or reducing costs?
We should assess this holistically, especially how we will need it for more tools like quests and folders of files.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For streams, we currently load all particles for the stream. Should we load a count and current index and then only load the particles that are nearest? Or have pagination so only show a few bars and then one color bar that indicates that there are more pages?
For now, maybe we are fine with loading all, and we won't have any performance issues with our current product? No need to optimize for some outlier case of running out of memory here or reducing costs?
We should assess this holistically, especially how we will need it for more tools like quests and folders of files.