3 ms·
The problem you describe is more about alignment between implementation and use cases. e.g. if your main use case is to have the data displayed on screen to be
by tuyiown 2y ago
The problem you describe is more about alignment between implementation and use cases. e.g. if your main use case is to have the data displayed on screen to be loaded, then that should be loaded. If it's desirable to preload other data in the background for later screen updates then just do that. The idea is more about first intent, load what is displayed on screen, if it's better to have parts loaded incrementally, then just do that.
- viraptor 2y agoThat's why I was asking about you stressing "must". In that case it's a mix of fetch before the screen, fetch to replace placeholders, fetch details on demand. That sounds like it breaks your "most fetch before rendering" rule.