4 ms·
Great, now let's go and build websites that don't require 100 request per page.
by dna_polymerase 7y ago
Great, now let's go and build websites that don't require 100 request per page.
- unilynx 7y agoWell, this might remove one argument against splitting the JS bundles too far. If you'll never benefit from eg. a shared JQuery library on a CDN anyway, might as well include a (reduced) version of it in your bundle.
- james-skemp 7y agoThat's as long as the shared library is changing about as frequently as your custom code. If you're using the same framework-x.y.z library for months at a time, but doing daily/weekly code changes and pushes, you're losing out on the cachability of the library. But if your project is only being updated as frequently as the third party libraries it uses, maybe it makes sense.
- QuadrupleA 7y agoBut the future is single-page apps with 500MB JavaScript bundles, and Rube Goldberg microservices with 2000 dependencies that need containerization to keep from breaking everything else on the server. Bro.
- marcus_holmes 7y agoMy thought exactly. JS devs have told me for years that the fact that their site uses >1Mb of JS script doesn't affect performance because almost all of it is already in the cache for 90% for users. Now there's a counter-argument and we'll get back to reasonable page sizes.