3 ms·
CDNs only embolden developers to pile up more and more resources on a page. Good thing to see it go away. And maybe they made sense for things like JS in the 2
by buboard 7y ago
CDNs only embolden developers to pile up more and more resources on a page. Good thing to see it go away.
And maybe they made sense for things like JS in the 2000s but many super-cheap hosting providers provide unmetered bandwidth nowadays. (and OF COURSE the privacy/security things)
- iforgotpassword 7y agoBut I assume that unfortunately web devs will still keep using cdns for all their libs since this is now industry standard and shows how pro you are.
- wilsonrocks 7y agoUnless the libraries are bundled in, which is the case for most of the stuff I use? Exception - the analytics stuff I'm obliged to add.
- iforgotpassword 7y agoYou're right, I think I mostly see fonts from Google and trackers nowadays.
- hinkley 7y agoIt also made sense when everything was HTTP 1.1, but that’s on the way out too. Browsers throttled the number of requests per domain because parallelism was expensive for the servers. Loading from another domain could happen simultaneously. If you had a fast internet connection you’d see a reduction in page load time. You’d also see that to a lesser extent if your connection was shared with others.