3 ms·

Seeing this, it reminded me of an interesting topic: caching at browser-level the common external JS libraries, to achieve big performance improvements: https:/

• e1g 4y ago
  And that reminds me of the rebuttal: such "embedding/blessing" of libraries would give them a considerable tailwind and stifle innovation. Suppose React/styled-components/Apollo/Highcharts is already available on the client. In that case, it becomes much harder to consider alternatives, and any new contenders (Vue/Solid/urql/emotion/etc) would never get traction.
  • chrisweekly 4y ago
    Yeah, cross-domain public caching had mostly theoretical benefits and never really worked that well in praxis. Glad browser vendors moved away from it.
    • Mystery-Machine 4y ago
      I'd like to read mor about why it only has theoretical benefits. Do you have any links to share where I can learn more? Thanks!
      • XCSme 3y ago
        Check the link in my top comment. Most problems are related to the privacy. A website could always tell if you loaded the resource or had it in cache. If you had it in cache, it means you have previously visited a website that used the same library. Now, if multiple such inferences can be made, it could be used for many things like fingerprinting, for marketing purposes, for identifying a user's identity, etc.