3 ms·

Yes, I should implement scorched-earth cache busting and force a complete reload of all bundles, because one craptastic browser relies on aggressive caching so

• foota 6y ago
  ... Yes? I mean, if you're not whole into the js ecosystem you can just use a cache buster parameter on your js requests in development, but I think the recommended approach is to use module splitting so that parts of the bundle that don't change remain the same. Alternatively if you just hate caching you can set cache control headers on your js. I think tying caching behavior to Google's web sites is silly, caching is a crucial part of performance for any heavy web application.
  • rangoon626 6y ago
    ... No. Every other browser seems to find a sane middle ground. Anyway this was never about my own practices, this was about how Chrome has become annoying and how it will result in attrition. The faster this happens, the better.