4 ms·
External libraries often introduce unused methods, thus expanding the size of your size, which could be problematic on high traffic size. So, if your site is s
by asdojasdosadsa 8y ago
External libraries often introduce unused methods, thus expanding the size of your size, which could be problematic on high traffic size.
So, if your site is small and has medium to low traffic, there's not really a "good" reason.
But if you have high traffic you might want to really squeeze every saving you can
- ddebernardy 8y agoIf you intend to write ~5-10k of custom JS that users will need to download over some potential high traffic scenario to get rid of a ~29k gzipped dependency that is almost certainly cached already because hosted on Google's CDN or elsewhere, you might want to look at your stats and see how much caching is going on before giving this a go. (The article says: "[...] when you consider that we have over 5 million pageviews to the article content type in any given 30 days, it translates to roughly 150GB of bandwidth saved." But that is utter BS that wouldn't pass a sniff test with a 10-year old who understands a modicum of browser caching and network caching.)
- stephenr 8y agoYour whole rant assumes using jquery from a CDN. While common, it’s not the only way to use it.
- reaperducer 8y agoYep. We are prohibited from using outside CDNs for security reasons.