3 ms·
Nothing is ever really cached anymore, meaningfully at least. We're in an age where websites happily serve up 8mb JavaScript bundles to display their static ho
by jasonkester 8y ago
Nothing is ever really cached anymore, meaningfully at least.
We're in an age where websites happily serve up 8mb JavaScript bundles to display their static homepage to a mobile browser that has maybe a couple hundred MB allocated to caching things. Sure, it may be there if you immediately load another page on that site (and the devs aren't using a bundler that serves a different 8mb next time).
But if they leave and come back, they'll get the same full download experience.
- jefftk 8y agoFor what it's worth, I run a/b tests in my work where I consistently see large caching effects. For example, when we compare an experimental version of something to the currently deployed version it's critical that we cache-bust the control group. And changes that improve caching generally make things significantly better. Caching effects are much smaller on Safari with its per-domain cache, but even there if something broke caching for us it would be a high priority to fix. (I work at Google on ad tags)
- reaperducer 8y ago8mb JavaScript bundles to display their static homepage to a mobile browser that has maybe a couple hundred MB allocated to caching things Thanks for that. It explains why even on very high-end new phones, switching between complicated web sites in different tabs causes a reload.