3 ms·
The original idea was that a shared source would mean the browser only caching a single copy of the code. Why should your cache contain 100+ identical copies of
by colejohnson66 2y ago
The original idea was that a shared source would mean the browser only caching a single copy of the code. Why should your cache contain 100+ identical copies of jQuery just because they were served on different URLs?
However, since cache partitioning, this benefit no longer exists.
- ASalazarMX 2y agoAnother benefit was speed, since a CDN was supposed to serve content faster than your server because it is a distributed network of servers. Probably not an advantage today with current speeds, unless you use dozens/hundreds of libraries a la Node.JS
- nirui 2y agoI would argue that self-hosting hundreds of Nodejs modules might still be a better choice than the alternatives, specially since it give a easier time for bundling tool such as Webpack to workout what it needs to do in order to bundle the project in a better way. And, let's don't forget creating a self-hosted CDN service to serve those bundles is not really THAT hard. (also creates job ops)