This falls apart when you consider one common scenario:
We are loading a number of data files and the source of truth is remote. This is O(n) the amount of data.
Two ways to do it: always request the remote data, or cache it, and only ask the remote for changes.
These differ by a constant factor, and it's always a good idea to maintain a local cache when it's possible. Otherwise there's a very good chance that startup time will be dominated by network requests.
But this also falls into “fantastically stupid” category. Just like all web 2.0 e-stores I have to use, which rerequest their dataset every time you touch sort or filter controls. When their largest category is 150kb json and the entire site json is 10x smaller than their ui/ad frameworks.
We are loading a number of data files and the source of truth is remote. This is O(n) the amount of data.
Two ways to do it: always request the remote data, or cache it, and only ask the remote for changes.
These differ by a constant factor, and it's always a good idea to maintain a local cache when it's possible. Otherwise there's a very good chance that startup time will be dominated by network requests.